feat: utilize moon for monorepo management

[gebhardtr]

Description

Make management of poloyglot servers easier with the moon monorepo framework.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[gebhardtr]

required until moon can handle version ranges, like the following, properly in the project dependencies:

oracle-mcp-common>=0.1.2,<0.2.0

[AlaaShaker]

It's a small change but might be worth fixing before we merge.

[dustin-sale]

Almost there, the build step in the Makefile will end up passing the common package to the same generate_package_metadata.py script as the rest of the mcp servers. This script does not support the common package properly.

[gebhardtr]

#427 simplifying package version handling in order to simplify this PR

[dustin-sale]

Sigh, one more thing. Can you add the moon.yml files to the exclude section under [tool.hatch.build.targets.sdist] in each pyproject.toml file?