{Pipeline} print stacktrace when exception

[qwordy]

I met an error in CI checks. I cannot reproduce it in my machine. So I edit pipeline in order to show the detailed error.

---

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

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[azuresdkci]

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:

docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/qwordy/azure-cli-extensions.git@alertsmanagement-phase1#subdirectory=src/$EXT&egg=$EXT"

[yungezz]

why speific this error? what about other errors?

[qwordy]

It raises this kind of error when it fails according to the doc. It's not recommended to catch a too-broad exception.

[haroldrandom]

It didnt' trigger the desired job runs on alertsmanagement extension.

[qwordy]

It didnt' trigger the desired job runs on alertsmanagement extension.

I am modifying pipeline definition to show the error. It does not aim to trigger the failed doc job.

[haroldrandom]

It didnt' trigger the desired job runs on alertsmanagement extension.

I am modifying pipeline definition to show the error. It does not aim to trigger the failed doc job.

This job verify extension ref should include alertsmanagement like other extensions, but missing: