Fix portal-first Foundry project linking

[Ananya Ghosh Chowdhury (ananyagc5)]

Summary

Fix the portal-first Lab 05 handoff so scripts/link-portal-rg.sh writes the Foundry project metadata expected by Bicep and the azure.ai.agents azd extension.

• Normalize Azure CLI's account/project response to the child project name before setting AZURE_AI_PROJECT_NAME.
• Persist AZURE_AI_PROJECT_ID, AZURE_AI_FOUNDRY_PROJECT_ID, AZURE_AI_PROJECT_ENDPOINT, and FOUNDRY_PROJECT_ENDPOINT.
• Prefer the project's location over resource-group metadata when setting AZURE_LOCATION.
• Add a mocked regression test for the qualified-name response and metadata aliases.
• Update Lab 05 instructions, the course spec, and the canonical plan with a pre-provision verification checkpoint.

Related issue and end-to-end reproduction: nitya#6

Validation

• pytest -q -> 16 passed on the latest microsoft-foundry:code-club-2026 base
• bash -n scripts/link-portal-rg.sh -> passed
• Patched linker run against rg-contoso-travel discovered contoso-travel-foundry1/contoso-travel-project and stored AZURE_AI_PROJECT_NAME="contoso-travel-project" with matching ID and endpoint aliases.
• azd ai project show resolved the current project endpoint immediately after linking.
• azd provision --preview --no-prompt succeeded and skipped the existing resource group, Foundry account/project, and container registry.
• End-to-end validation completed azd provision, deployed contoso-travel-concierge version 1, reported status active, and returned the expected CT-FL-014 response from remote invocation.