FIX: use a nightly spec.types.ts

[mattzcarey]

CI is failing due to a change in https://raw.githubusercontent.com/modelcontextprotocol/modelcontextprotocol/266e9a86edbe590bfa8d34d89527d70793b3ce53/schema/draft/schema.ts which is getting pulled into our spec.types.ts

This PR moves to a Nightly cycle where every day an action runs checking that file for changes and opening a PR. Because that file now lives in this repo we shouldn't see flaky CI runs.

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• 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 change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[pcarleton]

Love it, thanks. Is there a way to test run it pre-merge?

[mattzcarey]

Not really. There is a Docker based Github runner thingy but it wont deal with permissions issues which is probably the main worry here. I have tested it locally as a script and it runs fine but I can't test it with the Github token associated with the Github bot account. When you merge you can run the action manually to confirm. It should be fine tho I back it :)

[felixweinberger]

Thanks @mattzcarey!