Write an uber article or series of article on working with databases in aspire

[davidfowl]

We've gotten lots of feedback about the documentation on working with database in aspire being pretty fragmented, (see https://www.youtube.com/watch?v=uIN7iEsRkS4&feature=youtu.be for some details).

Some of the things we need to address:

1. How to use external database tools with aspire's database containers (SSMS, Azure Data Studio)
   • This includes fixing the port and potentially the password
2. How to use the built-in database tools (for databases that have it pgadmin)
3. How do you use aspire with an existing database.
4. How to use volumes to keep the data around.
   • When you use volumes, how do you reset/clear them?
   • Tell users that the password is stored in the volume. If you use a volume and change the password, it will not work until you delete the volume.
5. Using databases as persistent containers vs volumes?
6. How do you seed databases for development/deployed scenarios?
7. How do you use EF and aspire together?
   • Common pitfalls (inability to use dotnet ef to run migrations because there's no connection string)
   • What are the various ways to use EF migrations in Aspire and what are the tradeoffs (local dev vs deploying an app)

I think some of these can be solved as part of our improved integration docs issue but I think we need some top level conceptual content to address this area where we get lots of feedback.

We should prioritize Postgres and SQL server.