[WIP] Refactor configuration file management for a2a servers

[Claude]

• Research Azure storage options and understand current code structure
• Create configuration loader that supports both local files and Azure Blob Storage
• Add Azure Blob Storage SDK dependencies
• Implement configuration caching and hot-reload capability
• Add health endpoint to check configuration source and last reload time
• Create documentation for Azure setup (blob container, permissions, etc.)
• Test with local files to ensure backward compatibility
• Create example configuration for testing with Azure Dev Tunnels

Original prompt

This will be all only inside of src/a2a_servers. You can however look at /projectOverview.md to see how it fits into the whole project.

Right now a2a_servers is able to set up multiple a2a servers at once with different paths. It does through configuration files in a directory called src/a2a_servers/agents. But this means it is currently part of the code being deployed to azure as an azure app service web app. So if I want to add another agent or change a small configuration I have to completely redeploy the whole server.

Your task is to find a way to separate the configuration files so they can be decoupled and deployed separately on azure. You should find out the best way to host it, make sure to take a look at the configuration files and how they get used first. You most likely won't be able to fully set up the azure environment, that is okay as long as you provide a document explaining what I need to do. You should however setup the code to be able to read the files from azure once it would be there. There should also be a way to test the files hosted locally, wether that be through azure dev tunnels or some other method

The goal is to be able to easily edit the agent configurations and be able to quickly see the effects