Ensure we're also testing extensions in isolation to validate dependency issues in CI

We should look at smoke tests for extensions to be validated in isolation. There was a recent issue with a misconfigured dependency in azure.ai.agents that was covered up if you installed the microsoft.foundry meta extension and it pulled in everything.

We should see what we can do automatically and what we should do by convention/guideline.

Start by locating the extension smoke tests and the CI configuration, then review how the microsoft.foundry meta extension can mask a dependency problem in azure.ai.agents. Define whether isolated validation can be automated or should be a guideline; done means the approach is documented and catches misconfigured extension dependencies in CI.

Written by the indexing model from the issue text.