feat: add local PF code tools

[Hyperkid123]

Closes #18

This is a draft of a proposal for tools that return component information based on a locally installed PF package.

Changes

• adds getAvailableModulesTool that tries to resolve the local version of react-core, table, icons,data view*, component groups **, and lists available exports
• add getComponentSourceCode that returns the source code of a specific component

* The data view will require this PR to be merged: patternfly/react-data-view#551
** Component groups will require this PR to be merged: patternfly/react-component-groups#843

Preview

Preview from the mcp inspector

[cdcabrera]

@Hyperkid123 nice concepts!

Just a heads up

• Limited reviewing this week..
• On the roadmap for the short term tool plugins...

This will will affect what you're aiming for...

Our short term roadmap...

"Reduce maintenance overhead of the codebase and offset that onto "tool plugins" instead."

This is being done because

• we can't anticipate every use case
• provides an avenue for someone to use something outside of the releases, faster than we can
• reduce the "maintenance" and "testing" overhead on core
• creates a process that allows someone to move tooling plugins into core

How that might affect this work...

• let's you create a plugin(s) that
  • could be installed via NPM inside this repo
  • or immediate CLI or programmatic use, (closest example is the component schemas work where we started the concept)
• contributed utility functions to core that we may be able to expose back to tool plugins since their benefit might help other authors

The work for plugins was scheduled for last week, but it got pushed due to delays. The work you've got are some unanticipated concepts, very nice! Keeping the PR/MR up gives a testing framework for sure but when the work lands for the tool plugins we may encourage its use (next week).