Adding support for maintenance configuration for SQL DB

[hotsnr]

Description

• Added MaintenanceConfigurationId to 'New-AzSqlDatabase', 'Set-AzSqlDatabase', 'New-AzSqlElasticPool' and 'Set-AzSqlElasticPool'
• Logic completes public configuration name to full resource id if not full resource id specified
• The same thing as for Managed Instance - New parameter (MaintenanceConfigurationId) added to the New-AzSqlInstance and Set-AzSqlInstance cmdlets. #13395

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here

[msJinLei]

Please add the description to the https://github.com/hotsnr/azure-powershell/blob/rokhot/sqldb-maintenance/src/Sql/Sql/ChangeLog.md
Please note your description item should the first time under upcoming release.

[hotsnr]

Please add the description to the https://github.com/hotsnr/azure-powershell/blob/rokhot/sqldb-maintenance/src/Sql/Sql/ChangeLog.md
Please note your description item should the first time under upcoming release.

I edited that file, do you mean that it should be the first line in 'Upcoming release' section? I didn't see such requirement in the guide.

[msJinLei]

Please add the description to the https://github.com/hotsnr/azure-powershell/blob/rokhot/sqldb-maintenance/src/Sql/Sql/ChangeLog.md
Please note your description item should the first time under upcoming release.

I edited that file, do you mean that it should be the first line in 'Upcoming release' section? I didn't see such requirement in the guide.

When we are in the process of the release, new PR should the put its description item to the top of the upcoming release to avoid merge issue when release branch is merged back if there are other description items under the upcoming release.