Create deno.yml

[B-Scott33]

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

[Copilot]

Pull Request Overview

This PR adds a GitHub Actions workflow for continuous integration with Deno. The workflow is designed to automatically run linting and testing for Deno projects on pushes and pull requests to the main branch.

Key Changes

• Creates a new CI workflow that runs on Ubuntu with Deno v1.x
• Implements automated linting with deno lint and testing with deno test -A
• Includes security best practices by pinning action versions to specific commit hashes

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[richardkmichael]

@B-Scott33 Hello! Could you explain more about the intent here? Every type of change has been indicated, which is confusing. Is Deno compatibility being tested in a fork and a PR was accidentally opened?