Address python warnings from comment blocks in resource-graph extension

[yangmsft]

---

After AZ CLI 2.65.0 there is a Python warning originating from some comment sections in resource-graph extension, due to backslash escaping:

C:.azure\cliextensions\resource-graph\azext_resourcegraph\vendored_sdks\resourcegraph\models_models_py3.py:53: SyntaxWarning: invalid escape sequence '\ '
"""An interval in time specifying the date and time for the inclusive start and exclusive end, i.e. [start, end).
C:.azure\cliextensions\resource-graph\azext_resourcegraph\vendored_sdks\resourcegraph\models_models_py3.py:1196: SyntaxWarning: invalid escape sequence '\ '

The comment block involving backslash is largely redundant, hence this PR removes it. This does not change code logic in any way.

Related command

az graph

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]

Hi @yangmsft,
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.

[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]

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