Admin & Maintenance App: bot fleet CRUD

[CarsonL15]

Summary

Adds the Admin & Maintenance App: a React SPA at admin-webapp/ for staff to manage the delivery bot fleet. Closes #48, #49, #50, #52. Tracks parent issue #18 (still open: Orders,
Configuration, sign-in, and telemetry stories remain).

Every create / edit / delete double-writes to BotNet API (registry of record) and the Robot Simulator (runtime state), using the bot's name as the bridge key. Partial failures surface in
the UI as a yellow banner so the operator can see when the two systems disagree.

What's included

• React 19 + Vite 8 SPA with Bot Management page, add/edit dialog, delete confirmation, row-level actions
• API clients for BotNet (src/api/bots.js) and Simulator (src/api/simulator.js) plus an orchestrator (src/api/admin.js)
• 13 Vitest unit tests covering the double-write scenarios and slugifier
• Terraform module at Iac/admin-webapp/ that provisions WA-DeliveryBot-Admin-dev (reuses the existing App Service Plan)
• GitHub Actions workflow AdminWebpage-Deploy-WF.yml that auths via OIDC, runs Terraform, builds, and deploys

Resources Used

• Azure App Service (WA-DeliveryBot-Admin-dev, Canada Central, Linux Node 22)
• Azure App Service Plan (ASP-RGDeliveryBotdev-8b82, reused)
• Azure Storage Account (dbstfstate01, reused for Terraform state)
• Container Apps (BotNet API + Simulator, consumed)
• GitHub Actions OIDC federated identity
• Terraform 1.9 + AzureRM Provider 4.x
• React 19, Vite 8, Vitest 2, Node 22

Known gaps

• CORS allow-list on BotNet / Simulator needs the admin origin once it's deployed
• Auth (Entra ID, story Sign in as staff (Entra ID) #54) and live telemetry feed (story Live telemetry feed #55) are still in the backlog under Admin and maintenance app #18
• Orders tab and Configuration tab in the admin app are placeholders; they belong to the rest of Admin and maintenance app #18's scope