AddSqlServerDbContext forces you to use AddDbContextPool

[DKANomad]

I have been experimenting with Aspire and found a bit of an inconsistency in the docs and that API.

According to this page the DbContextPooling is a configuration option, however looking at the code I can see this isn't the case.

I'm wondering if this was a decision that was made to force context pooling, and if so I'd like to discuss changing back to it being a configuration option.

Reason being that the limitation around the access of scoped services when using context pooling. I like to leverage query filters in cases where I want to force all queries to use include a TenantId filter which requires access to a service that I can set a value in via middleware.

I wasn't sure if this would be considered an issue or if it required more conversation first.