Move all packages that use core-http to use the newer Azure Core packages

[ramya-rao-a]

We started out shipping the newer packages in November 2019 that all used the @azure/core-http package mainly that implemented pipelines and policies for making http requests. See the readme for core packages for more details.

Earlier this year, we shipped Azure Core 2.0 for JS SDKs

In May 2021, we shipped a new version of our SDK generator that supports these newer core packages by default with an option to use the older core-http

This issue is to track the work needed to ensure all our packages have been upgraded to use the new Azure Core v2.
We documented one of the package moves in a wiki which you can refer to for changes you may want to do in the hand written layer of your package to avoid any breaking changes for your customers. See core http dependency migration to core client core rest pipeline

Packages that already use the newer Azure Core v2 packages, but should be upgraded to use the output of the latest version of our SDK generator

• Tables [Tables]Move the Tables package to use core-rest-pipeline #15824
• Event Grid [Event Grid]Move the Event Grid package to use core-rest-pipeline #15823
• Azure Container Registry (blocked until CAE feature in core-rest-pipeline goes GA) [Azure Container Registry]Move the Azure Container Registry package to use core-rest-pipeline #15822
• Text Analytics

Packages that use the older core-http, but not the code generator and should upgrade to use the newer core packages

• Template Update template project to use corev2 #18044
• Identity [Identity] Move the Identity package to use core-rest-pipeline #15595
• Service Bus [Service Bus]Move the Service Bus package to use core-rest-pipeline #15821

Packages that use the older core-http, have a convenience layer over generated code and should be upgraded to use the output of the latest version of our SDK generator. You most probably have a swagger/README.md file where you have configured the use-extenstion argument to a version of @autorest/typescript. Update this to the latest beta version of https://www.npmjs.com/package/@autorest/typescript and re-generate your code

• App Config [App Config]Move the App Config package to use core-rest-pipeline #15809
• Form Recognizer [Form Recognizer]Move the Form Recognizer package to use core-rest-pipeline #15810
• Metrics Advisor [Metrics Advisor]Move the Metrics Advisor package to use core-rest-pipeline #15811
• Search [Search]Move the Search package to use core-rest-pipeline #15812
• Attestation
• Storage [Storage]Move the Storage package to use core-rest-pipeline #15813
• Key Vault Admin [Key Vault] Move one Key Vault package to use core-rest-pipeline #15522
• Key Vault Keys, Secrets and Certificates Move remainder of Key Vault packages to core-rest-pipeline #15896
• Communication [Communication]Move the Communication packages to use core-rest-pipeline #15814, Update the new @azure/communication-network-traversal package to use the latest code generator #18689, Update the new @azure/communication-short-codes package to use the latest code generator #18688
• Monitor (exporter & query) [Monitor]Move the Monitor package to use core-rest-pipeline #15815
• Digital Twins [Digital Twins]Move the Digital Twins package to use core-rest-pipeline #15816
• Mixed Reality Auth [Mixed Reality Auth]Move the Mixed Reality Auth package to use core-rest-pipeline #15817
• Video Analyzer [Video Analyzer]Move the Video Analyzer package to use core-rest-pipeline #15818
• Web Pub Sub [Web Pub Sub]Move the Web Pub Sub package to use core-rest-pipeline #15820
• Schema Registry [Schema Registry] Migrate to core v2 #16519

Rest of the packages that are currently purely auto-generated and so will automatically get updated the next time there is a swagger update

Benefits of the move can be found in https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/core/core-rest-pipeline/documentation/core2.md