[ai agent extension] add support for publishing a hosted agent in Foundry

[therealjohn]

Add support for the publish flow of a hosted agent: Use the Microsoft Foundry azd agent extension | Microsoft Learn

Publish the agent: Create an Agent Application in Microsoft Foundry and deploy the agent as a live, callable service.

Here's an example of the resource needed: foundry-samples/samples/csharp/FoundryA365/infra/modules/application.bicep at main · microsoft-foun…

The Portal produces a stable endpoint that you can call for /responses and /activityprotocol

[therealjohn]

Prototype: therealjohn@373e6d6
Infra required: therealjohn/foundry-agent-application@295d240

Initial azd up commands deploy only the agent. When ready, do azd env set ENABLE_APPLICATION true. This controls conditional bicep so that the Foundry Agent Application is provisioned. Similarly, azd env set ENABLE_BOT_SERVICE true can be set for the A365 digital worker.

This reproduces a CLI driven way to Publish and Publish to Teams/M365, like you can in the portal:

Once the env var is set, azd up/deploy will show the endpoints:

the AZD AI Agent extension hooks are used to do the deployment of the agent application.
Required parameters are pulled from the agent.yaml and set as env vars AGENT_NAME, APPLICATION_NAME which default to the name in the agent.yaml.

TODO: Decide if we need azd ai agent publish or another way to detach this from the inner loop so you wouldn't need to toggle ENABLE_APPLICATION if you don't want to publish, OR if you need to make a different version the "published" agent.

[therealjohn]

New agents (vnext backend) will automatically get a stable endpoint and an application resource is no longer needed.