Move m2r code into autorest.python

[catalinaperalta]

Related to microsoft/typespec#6091

[catalinaperalta]

Temporarily pinned the http-client-python dependency to the artifact created in ci by the PR I linked above. After the typespec pr is merged in and released I'll revert that change.

The autorest.python checks show a test failing, any advice on how to make that one pass? It doesnt look like it's related to the m2r changes.

I tried to run npm run test locally but get this error:

> npm run test

> @autorest/python@6.29.0 test
> tsx ./scripts/eng/run-tests.ts --validFolders azure/legacy azure/version-tolerant vanilla/legacy vanilla/version-tolerant dpg/version-tolerant

Running ci for folder azure/legacy...
'FOLDER' is not recognized as an internal or external command,
operable program or batch file.
Command failed: FOLDER=azure/legacy tox -c ./test/azure/legacy/tox.ini -e ci
Error executing command for folder azure/legacy: Command failed: FOLDER=azure/legacy tox -c ./test/azure/legacy/tox.ini -e ci
npm error Lifecycle script `test` failed with error:
npm error code 1
npm error path C:\Users\caperal\repos\autorest.python\packages\autorest.python
npm error workspace @autorest/python@6.29.0
npm error location C:\Users\caperal\repos\autorest.python\packages\autorest.python
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c tsx ./scripts/eng/run-tests.ts --validFolders azure/legacy azure/version-tolerant vanilla/legacy vanilla/version-tolerant dpg/version-tolerant

NOTE: the typespec checks are failing because when using the artifact download link some file paths are too long during regeneration.

cc @msyyc hopefully you can take a look on your Monday

[msyyc]

Temporarily pinned the http-client-python dependency to the artifact created in ci by the PR I linked above. After the typespec pr is merged in and released I'll revert that change.

The autorest.python checks show a test failing, any advice on how to make that one pass? It doesnt look like it's related to the m2r changes.

I tried to run npm run test locally but get this error:

> npm run test

> @autorest/python@6.29.0 test
> tsx ./scripts/eng/run-tests.ts --validFolders azure/legacy azure/version-tolerant vanilla/legacy vanilla/version-tolerant dpg/version-tolerant

Running ci for folder azure/legacy...
'FOLDER' is not recognized as an internal or external command,
operable program or batch file.
Command failed: FOLDER=azure/legacy tox -c ./test/azure/legacy/tox.ini -e ci
Error executing command for folder azure/legacy: Command failed: FOLDER=azure/legacy tox -c ./test/azure/legacy/tox.ini -e ci
npm error Lifecycle script `test` failed with error:
npm error code 1
npm error path C:\Users\caperal\repos\autorest.python\packages\autorest.python
npm error workspace @autorest/python@6.29.0
npm error location C:\Users\caperal\repos\autorest.python\packages\autorest.python
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c tsx ./scripts/eng/run-tests.ts --validFolders azure/legacy azure/version-tolerant vanilla/legacy vanilla/version-tolerant dpg/version-tolerant

NOTE: the typespec checks are failing because when using the artifact download link some file paths are too long during regeneration.

cc @msyyc hopefully you can take a look on your Monday

I commit some fix to fix the CI.

[catalinaperalta]

Thanks for helping with this PR @msyyc!!