Don't set properties on existing Azure SQL server resources

[captainsafia]

Description

Avoid setting fields that will be emitted in the properties of the Bicep file for Azure SQL server resources that already exist. Instead, add a SQL Admin through SqlServerAzureADAdministrator child resource.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

[eerhardt]

FYI @tg-msft - this is how we figured to work around this issue.

[eerhardt]

@tg-msft this is the workaround, notice we don't call base here. We just define the 4 properties we need.

[eerhardt]

LGTM. Thanks for the fix!

Hopefully we can remove the workaround once the Azure.Provisioning issue is fixed.

I think we should backport this to 9.1.

[captainsafia]

/backport to release/9.1

[github-actions]

Started backporting to release/9.1: https://github.com/dotnet/aspire/actions/runs/13428002254