Add metadata to create message

[dtrugman]

Related GitHub Issue

Closes: #3830

Description

This is the suggested implementation for feature #3830.
Should make it easier to evaluate.

Test Procedure

Unit-tests should pass.
Should have no-impact otherwise.

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

No UI changes.

Documentation Updates

Does this PR necessitate updates to user-facing documentation?

• No documentation updates are required.
• Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs repository).

Additional Notes

N/A

---

Important

Add optional metadata to createMessage function across various API handlers to enhance API request capabilities.

• Behavior:
  • Add optional metadata parameter to createMessage function in ApiHandler interface in index.ts.
  • Pass metadata to API requests in createMessage implementations in anthropic-vertex.ts, anthropic.ts, and base-openai-compatible-provider.ts.
  • Update createMessage in Task.ts to include mode and taskId in metadata.
• Providers:
  • Modify createMessage in anthropic-vertex.ts, anthropic.ts, base-openai-compatible-provider.ts, and 15 other provider files to accept metadata.
• Misc:
  • Add ApiHandlerCreateMessageMetadata interface in index.ts to define metadata structure.

^{This description was created by for 7c68cc05bb320e7d7b7c3f93e8ff2eab9b8fd971. You can customize this summary. It will automatically update as commits are pushed.}