{Service Connector} fix compatibility issue and refactor

[xfz11]

Refactor the firewall updates rule

• First, get the local IP address from websites
  • If it succeeds, try to add the local ip address and connect
  • If it fails, try to ask user to input local ip address (added)
    • If user input a valid IP, add it to firewall. Else, keep asking for a valid IP
    • If user choose to add all ip address, add all IP range to firewall
    • If user have no TTY, throw exception and fail
• If user local IP address is not working, prompt a confirmation to add all IP
  • If user approve, add all IP and retry to connect
  • If user reject, fail the command

@houk-ms the refactor detail. Add a fallback logic to ask for user input a local ip in the case IP can't got from 3rd party website.

---

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

Related command

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?

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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]

Hi @xfz11,
If you want to release the new extension version.
Please write the description of changes into HISTORY.rst and update setup.py.

[yonzhan]

Service Connector

[houk-ms]

Can you give some desciptions on what changes are made in this PR?

[azclibot]

[Release] Update index.json for extension [ serviceconnector-passwordless ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=62555&view=results