Bicep MCP Server HTTP Transport

As requested in the community call

**Is your feature request related to a problem? Please describe.**
Some companies start to restrict local MCP server running with stdin an stdout.

**Describe the solution you'd like**
It would be great if we can centrally host the MCP server by utilising the HTTP transport to the MCP server.
So if the MCP server supports HTTP would be awesome.

Start by locating the Bicep MCP Server entry point and its current stdin/stdout transport implementation; the issue names no files or tests. Define the HTTP transport requirements and verify that the server can be centrally hosted and accessed over HTTP instead of relying only on local standard input and output.

Written by the indexing model from the issue text.