Upgrade autorest

[DmitriyKirakosyan]

PR Summary

This PR presents a significant update to the codebase, primarily focusing on upgrading the autorest package to version 3, phasing out the deprecated and security risk-laden request dependency, and accommodating for the breaking changes including the shift from a callback-based API to a promise-based one.

Changes Implemented:

1. Removed request: All code has been updated to use fetch instead of request. I specifically chose to use node-fetch over alternatives such as got or axios primarily to avoid introducing additional dependencies and their subsequent cascading dependencies. Notably, node-fetch was already part of our existing dependencies.
2. Migrated ms-rest to ms-rest-js: As the ms-rest package listed request as a dependency, it has been migrated to ms-rest-js.
3. Upgraded autorest to version 3: The earlier used autorest version 2 utilized ms-rest, hence it was upgraded to version 3.
4. Updated Swagger API file: It's made compatible with the new autorest version.
5. Regenerated API files: The API files were regenerated using the updated autorest and Swagger API file.
6. Modified create-client class: Adjustments were made to build and use the new service client effectively.
7. Refactored Commands: All affected commands in the application have been modified according to the new API generated from the files.
8. Resolved Compilation Issues: All compilation errors arising due to these changes have been fixed.
9. Updated Tests: Tests have been updated to align with the new changes.

Reviewing This PR

Note: All files within "src/util/apis/generated/src" were auto-generated by autorest using the "scripts/autorest.js" script and can be ignored during the review.

1. Begin with create-client class: This class is the foundation as it instantiates and configures the App Center client service used for API calls.
2. Review Changed Commands: Navigate through the modified commands in "src/commands" and look for any suspicious changes, such as code removal, missing blocks, or improper error handling.
3. Review Test Modifications: Examine the changes made to the tests.

Optional: If you have additional time, you can fetch and test these changes in your local setup. If you do so, please comment on this PR about the commands you managed to test, to help others focus on untested parts.

Related Work Items:

This PR is related to the following work items:

• Issue #761
• AB#101001

[AnatolyPristensky]

All affected commands have been tested. Approved.