Create improved workflow for remote MCP servers #1172
Description
Right now. ToolHive has a bunch of functionality for workloads created through ToolHive, and offers a proxy for remote MCP servers which does not have all the functionality available to local workloads.
We should implement a more seamless experience for remote MCP workloads. In order to simplify the internal implementation, I think we should treat remote MCP servers as a form of workload. This allows us to seamlessly support functionality such as client configuration, tool filtering, import/export etc. without having two different pathways through the code.
We should also provide a simple way of creating a workload from a remote URL, e.g.
thv run --remote <URL of MCP server>
As noted above, we should support import/export of remote workload configuration similar to the import/export of local workloads described in #1171