[PACKAGING] Fix: Use PEP 440 compliant version specifier for azure-cli-telemetry

[janjagusch]

Related command

Description

This PR changes the version specifier for azure-cli-telemetry. Previously, it used the ==X.Y.Z.* schema, which is a discouraged edge case of PEP 440.

• Find the PEP here.
• Find the discussion on the edge case here

To quote one of the PEP's authors (see here):

I don’t think myself or Nick considered at all the idea of something like ==1.1.0.post0.* for the PEP to have a thought one way or the other. I think that disallowing them makes the most sense though.

This PR replaces the version specifier with >=X.Y.Z,<X.Y.Z+1.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

---

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

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[azure-client-tools-bot-prd]

Validation for Azure CLI Full Test Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[microsoft-github-policy-service]

Thank you for your contribution @janjagusch! We will review the pull request and get back to you soon.