Refactor tests to merge multiple json files

[Cali0707]

To make it easier to extend toolsets in forks, like the openshift-mcp-server, we should refactor the mcp/toolset tests to:

1. Have tools from each toolset defined in it's own json file
2. Merge those tools into the final expected object based on which toolsets should be enabled in the scenario
3. Make assertions about equality

[Cali0707]

cc @manusa @matzew

[manusa]

The tests already have each toolset defined in its own toolset json file (1).

I'm assuming the related problem is about the toolsets-full-tools.json which has the combined toolsets.

Note that this IS NOT including all toolsets but the ones defined as enabled by default:

kubernetes-mcp-server/pkg/config/config.go

Line 76 in 86628bb

Toolsets: []string{"core", "config", "helm"},

I implemented these tests while creating the decoupled toolsets feature to ensure that the tool definitions remained constant.
I see how the full-tools toolset test is a pain for maintainers (the others too unless you know how to update the files).

We can either remove the full-tools test, add a flag so that the test is skipped downstream, find an alternative.
I personally like having those because it gives an extra degree of confidence.

[manusa]

OK; after checking the rest of the activity I can see better the issue now.

IMO downstream we should not mutate the existing toolsets, i.e. Don't add stuff to core, helm, config, etc.

If there's a need to extend one of the original toolsets, then just create a new one and add the extended tools. For example openshift-core.

Or created a granular one openshift-debug. With the isolated group of tools to add (then maybe add it to the default list of toolsets).

The idea of toolsets was to make them completely decoupled from the upstream so that downstream you could add separate directories and each toolset self-registred.

By following these principles, the only points of divergence are introduced in:

• pkg/mcp/modules.go.
  We can further mitigate this by creating an empty modules_downstream.go
• pkg/mcp/modules.go
  Could also be mitigated by creating a default config provider

[manusa]

The second commit in #396 should take care of the problem