[Recorder] Test proxy and the ports

[HarshaNalluru]

Recorder from the @azure-tools/test-recorder v2 package expects the test-proxy tool is run at the ports 5000 and 5001 (HTTP and HTTPS respectively).

It works because all the following commands run the test-proxy tool at those ports by default

• dev-tool run test:node-js-input
• dev-tool run test:node-ts-input
• dev-tool run test:browser
• docker run -v /workspaces/azure-sdk-for-js/:/srv/testproxy -p 5001:5001 -p 5000:5000 azsdkengsys.azurecr.io/engsys/testproxy-lin:latest
• test-proxy --storage-location

However, if the 5000 port is blocked on a client machine, they won't be able to run any of the above commands directly to run the test-proxy tool.
Meaning, the test-proxy tool needs to be run at a different port, but the test-recorder expects the tool runs at 5000, 5001.

TODO:

• Brainstorm and provide a pattern to remove the hard-coded port in the recorder package,
• Ports to be dynamic instead
• Make sure all the commands work in sync with the updates

[azure-sdk]

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.58147585,Storage:0.06634899,Cognitive - Form Recognizer:0.025332628'

[timovv]

Related: #18240

[HarshaNalluru]

#22145