Update Bicep template to reflect Azure Web App scale-up operation

[Copilot]

This PR updates the Infrastructure as Code (Bicep template) to accurately reflect the Azure Web App configuration after the scale-up operation described in issue #96.

Problem

The issue reported that Azure Web App "cpu-app" was scaled up from Standard S2 to Standard S3, but the Bicep template in the repository was out of sync with the actual deployed infrastructure:

• Template defined web app name as "test_webapp" instead of "cpu-app"
• Template used Free tier (F1) instead of the Standard S3 tier mentioned in the scale-up operation

Changes

Updated main.bicep to align with the actual deployed resources:

• Changed webAppName parameter from 'test_webapp' to 'cpu-app'
• Updated App Service Plan SKU from F1/Free to S3/Standard

Validation

• Bicep template compiles successfully to ARM template
• .NET application builds without errors
• Web app URL output now correctly generates https://cpu-app.azurewebsites.net
• Only minimal changes made (3 lines modified in 1 file)

This ensures the Infrastructure as Code accurately represents the post-scale-up Azure environment.

Fixes #96.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: bicep build main.bicep --outdir /tmp (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.