{CI} Add GitHub Action to Conditionally Trigger CI Based on Safe File Changes

[wangzelin007]

---

This PR introduces a GitHub Action that conditionally triggers the CI process based on specific file changes in the PR. The purpose is to avoid automatically running CI when potentially risky files, such as configuration files (*.yml) or files within the scripts/ directory, are modified. This helps mitigate unintended impacts from sensitive file changes by not triggering CI in those cases.

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? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

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]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @wangzelin007,
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]

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

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[wangzelin007]

@microsoft-github-policy-service rerun

[MoChilia]

request change