[ConnectedK8s] Add support for multiple proxy instances running on the same machine using different ports

[RyanBDB]

This PR addresses #6366

For our use case, it would be very helpful for the connectedk8s proxy to support multiple instances running on the same machine. This enables interactions/ control over multiple Arc connected Kubernetes clusters from the same machine by simply switching your kube context.

I've tested the change locally and been able to run multiple proxies on different ports and use kubectl to target multiple clusters by switching kube context.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az connectedk8s proxy

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @RyanBDB,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

ConnectedK8s

[RyanBDB]

Note, azdev style is failing, but the flagged issues are not par of the code changes in this PR.

[github-actions]

⚠️ Suggestions

Module: connectedk8s

• Update version to 1.6.8 in setup.py

Notes

• Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
• Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
• For more info about extension versioning, please refer to Extension version schema

[zhoxing-ms]

@darrendejaeger Could you please help review it again?

[azclibot]

[Release] Update index.json for extension [ connectedk8s ] : https://dev.azure.com/azclitools/release/_build/results?buildId=146822&view=results