azure-powershell Add TLS 1.3 to MinimalTlsVersion

Description

Mandatory Checklist

Please choose the target release of Azure PowerShell
- [ ] General release
- [ ] Public preview
- [ ] Private preview
- [ ] Engineering build
- [ ] N/A
[ ] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

SHOULD update ChangeLog.md file(s) appropriately
- For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
  - A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
- For autorest-based development mode, include the changelog in the PR description.
- Should not change ChangeLog.md if no new release is required, such as fixing test case only.
SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
SHOULD have proper test coverage for changes in pull request.
SHOULD NOT adjust version of module manually in pull request

Feb 12 '24 18:02 jha1bhavna

️✔️Az.Accounts

️✔️Az.Compute

️✔️Az.EventHub

️✔️Az.KeyVault

️✔️Az.ManagedServiceIdentity

️✔️Az.Monitor

️✔️Az.Network

️✔️Az.OperationalInsights

️✔️Az.PrivateDns

❌Az.Sql

️✔️Az.Storage

Feb 12 '24 18:02 azure-client-tools-bot-prd[bot]

Need to update Azure.Core version first

Feb 18 '24 03:02 msJinLei

Where do we update that? to what?

Feb 20 '24 04:02 jha1bhavna

The "Azure.ResourceManager.Sql" introduce the dependancy of Azure.Core 1.37, which conflicts with the exiting Azure.Core Azure PowerShell uses. What you depend on in Azure.ResourceManager.Sql. You should generate it in your generated SDK.

Feb 20 '24 07:02 msJinLei

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

Feb 20 '24 07:02 github-actions[bot]

Updated the Azure.Core version to 1.37

Mar 13 '24 12:03 jha1bhavna