[containerapp] Fix failing ACA apps when run together

[jepetty]

---

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

Related command

azdev test azext_containerapp

This isn't customer-facing at all. Running all containerapp tests with azdev test azext_containerapp fails for me (on multiple machines) because of application-insights extension installation. This (admittedly copilot generated) change fixes this (again, on multiple machines) so the test-suite can be run at once

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

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

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

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>

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[github-actions]

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

[Copilot]

Pull request overview

This PR adjusts the containerapp function tests so that the application-insights extension is installed once per test class (and only if needed), rather than on every test instance, to avoid failures when running the full azext_containerapp test suite together.

Changes:

• Introduced a setUpClass classmethod on ContainerappFunctionTests to probe for the application-insights extension via az extension show and install it with azdev extension add only when missing.
• Removed the per-instance extension installation and sleep from the __init__ constructor so tests no longer redundantly install the extension for every case.

[Copilot]

Catching a broad Exception here and silently doing nothing can hide legitimate setup problems (e.g. az/azdev not being available or the extension add failing) and make later test failures harder to diagnose. Consider narrowing the exception to the specific failure modes you expect (such as subprocess.CalledProcessError / FileNotFoundError) and at least logging a message when extension installation is skipped or fails.

[Greedygre]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).