bit Boilerplate needs several small enhancements #11512
Description
The bit Boilerplate template currently has several issues that impact its functionality, maintainability, and developer experience:
01- SignalR's HubConnection's On listeners are not properly disposed.
02- Duplicate sending of X-App-Version and X-App-Platform headers through SignalR client
03- Wasm SIMD is disabled in dev environment. Although having this option disabled is a good idea in environments other than dev env, because it would result into more browser versions supports thanks to Bit.BlazorES2019, but in dev env, it would trigger wasm native build which slows down project builds.
04- Due the fact that LocalTextEmbeddingGenerationService is a default embedding generator, the product's Embedding's size should be 384, because LocalTextEmbeddingGenerationService generates verctos with 384 dimensions.
05- Checking if client's version supported in AppHub is not revelant anymore, because #11502 is checking it in a middleware before SignalR
06- Due the fact that most embedding generators ignore EmbeddingOptions, this configuration section has to be removed.
07- The minio resource in aspire's app host project, has been renamed to s3, so the corresponding parameter for its password should also renamed in appsettings.development.json
08- Client wasm project must be explicitly started in aspire's app host rather than automatic start
09- health checks endpoints must be filtered from open telemetry logs
10- Blazor events such as onmousehover must filtered from open telemetry logs
11- In order to have consistent behavior, test initializer must use Database.EnsureCreatedAsync just like the entry points of Server.Api & Server.Web with a comment that would encourage developer to use migration.
12- Xamarin.AndroidX.SavedState.* are not required anymore.