Tech Debt - Improve how checking the status of the MCPServers with the gateway is handled

[maleck13]

What

Currently the controller sends a request to the broker to get the current status of that MCP Server and report it in the status of the MCPServerRegistration.

There is legacy code here from the POC that looks up the endpoint slice. Really it should be possible to just use the service name

Option

We could also remove the status checks from the controller. THe controller can consider the MCPServerRegistration complete once it has written the config for that MCP into the correct locations.

[david-martin]

Discussed on backlog refinement 3/3/26:

• this is worth exploring for the benefit of a less complex architecture in the controller and broker
• there is a knock on for the user as the status of the server registration is not as easily available
• e2e tests may need to change to rely on actual mcp calls rather than status
• users will need to rely on observability more (e.g. logs) and the /status endpoint
• config values in helm would be lessened