DotNetIntegratedVectorizationDemo seems not generating a search document for each chunk of the enriched data

[DotNetIntegratedVectorizationDemo](https://github.com/Azure/azure-search-vector-samples/blob/main/demo-dotnet/DotNetIntegratedVectorizationDemo/readme.md) seems not generating a search document for each chunk of the enriched data but only a search document for the unchunked documents. Should it follow the example of [postman-collection](https://github.com/Azure/azure-search-vector-samples/blob/692e2e38d5c29af8790b8280298a1e1f433730d9/postman-collection/AzureSearchVectors_2023-10-01-preview.postman_collection.json#L128C1-L129C1) to add [index projections](https://learn.microsoft.com/en-us/azure/search/index-projections-concept-intro?tabs=kstore-rest) to achieve that?

Start with demo-dotnet/DotNetIntegratedVectorizationDemo/readme.md and compare its setup with the linked postman collection around lines 128-129. Check whether the enriched, chunked data produces one indexed search document per chunk, and use the index projections documentation to determine whether that is the intended configuration. Done means the demo's behavior and configuration are corrected or the expected behavior is documented.

Written by the indexing model from the issue text.