Feature/sms core v2 and test recoder migration

[arifibrahim4]

Packages impacted by this PR

• @azure/communication-sms

Issues associated with this PR

• Migrate communication-common auth policies to Core v2 #20056
• Move all packages that use core-http to use the newer Azure Core packages #15594
• Core v2 migration @azure/communication-sms package and using new @azure/communication-common #20402

Describe the problem that is addressed by this PR

• https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/core/core-rest-pipeline/documentation/core2.md

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

• https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/core/core-rest-pipeline/documentation/core2.md

Are there test cases added in this PR? (If not, why?)

• Yes

Provide a list of related PRs (if any)

• [communication-short-codes] Migrate to Core v2 #19043
• Chat Core2 Migration #17045
• [Communication] - phone-numbers - Core V2 migration #20633
• @azure/communication-common Azure Core 2.0 Migration #20337

Checklists

• Added impacted package name to the issue description
• Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
• Added a changelog (if necessary)

[azure-sdk]

API change check for @azure/communication-sms

API changes have been detected in @azure/communication-sms. You can review API changes here

API changes

- export interface SmsClientOptions extends PipelineOptions { }
+ export interface SmsClientOptions extends CommonClientOptions { }

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci