Add documentation about limitations deploying containers with volumes on Azure container apps

[davidfowl]

See

• Postgres does not work with volumes when hosted on ACA aspire#6671
• Aspire Azure MySQL ACA Deployment fails on Startup with data dir error aspire#9230
• [preview 5] WithDataVolume breaks application when published to Azure aspire#3685

Containers that don't work with volumes (will make a full list)

• Postgres
• MySQL

[alistairmatthews]

@davidfowl I'm working on this. I'm going to add notes to the relevant integration docs and maybe the deployment docs to this effect:

• ACA uses SMB to connect to data volumes in containers. This is fine for SQL Server, but not supported by PostgreSQL and MySQL, which causes the error.
• Use Azure DB for PostgreSQL instead (or the equivalent managed DB service).

I'll do this for PostgreSQL and MySQL first, then test other things (e.g. Milvus? MongoDB?).

I think this will support persistence when running locally in a container:

var postgres = builder.AddAzurePostgresFlexibleServer("postgres")
     .RunAsContainer(ConfPostgresContainer);

...

static void ConfPostgresContainer(IResourceBuilder<PostgresServerResource> container)
{
    container.WithDataVolume();
}

[alistairmatthews]

PR #3706 fixes this issue. I also tested SQL Server, Redis, and Milvus integrations and didn't see this issue.