SDK update for "Support providing Salesforce passwords and security tokens as SecureStrings or as secrets in Azure Key Vault"

[wezou2]

Description

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[wezou2]

This PR has been internally reviewed and the corresponding release item is approved.

[shahabhijeet]

Add description that describes what is the entire change is all about.
Also add link to your PR

[bgold09]

approved via internal item 97519

[bgold09]

@wezou2 FYI you have merge conflicts

[smilenow]

Please look at #3824 to prevent double merging. I propose that close this PR after #3824 merged.