Updating fast-uri to 4.1.1 to the overrieds in files listed. While ad…

[tri-sa-rah-tops]

Pull Request Checklist

Please ensure that your PR meets the following requirements:

• I have read the CONTRIBUTING guide.
• I have updated the documentation (if applicable). -- N/A
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have added tests that prove my fix is effective or that my feature works. -- N/A as this is a dependency bump
• New and existing unit tests pass locally with my changes.

Description

Addressing this issue suggesting to update fast-uri to latest version. Also bumped ajv in one spot, since I noticed it wasn't consistent with other versions across the project. fast-uri is now updated to version 4.1.1.

Fixes #470

Type of Change

• 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

[CLAassistant]

All committers have signed the CLA.

[github-actions]

BLOCKING ```json
"@moss-dev/moss": "latest"

This lockfile now records `@moss-dev/moss` as `latest`, but the matching `package.json` dependency was not changed in this PR, so the lockfile no longer mirrors the manifest. `npm ci`/fresh installs can treat this as lockfile drift or rewrite it back. Regenerate the lockfile from the unchanged manifest, or update `examples/cookbook/mastra/package.json` intentionally and commit both files together.

[github-actions]

Codex review

The fast-uri override changes are mostly mechanical, but one lockfile was left out of sync with its manifest. That can make installs rewrite or reject the lockfile for the cookbook example.