[dev-tool] Create migration tool

[mpodwysocki]

Packages impacted by this PR

• @azure/dev-tool

Issues associated with this PR

Describe the problem that is addressed by this PR

Creates a starter migration toolkit for projects to move to ESM and vitest. This project for dev-tool introduces a tool invoked such as the following to migrate service-bus

dev-tool admin migrate-package --package-name=@azure/service-bus

This does the following:

• Changes the package.json for the following:
  • Removes chai/mocha/karma
  • Adds vitest and tshy
  • Modifies the build and test commands
  • Renames the mapped files to the proper output type such as -browser.mts
• Changes the tsconfig.json for the following:
  • Moves module and moduleResolution to NodeNext
  • Removes outDir and declarationDir
• Fixes the source files
  • Uses extension for files such as "foo.js" instead of "foo"
  • Removes "chai" usage
  • Adds vitest usage for spec files
• Fixes api-extractor.json
  • Fixes input path for source
  • Fixes output trimmed path
• Migrate Testing
  • Writes for both browser and node unit tests
  • Writes config for building browser bundle
  • Removes .nycrc and Karma configuration

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?

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

Provide a list of related PRs (if any)

Command used to generate this PR:**(Applicable only to SDK release request PRs)

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)

[maorleger]

🚀

[jeremymeng]

This is awesome!

[jeremymeng]

We can have incremental improvements to this tool later as we apply the migration to more packages. One example I can think of is to remove this: Mocha.Context or this: Context from test callbacks.