Add pathVariableNames and queryVariableNames getters in UriTemplate

[Mubashwer]

This PR adds two new getter methods to the UriTemplate class that distinguish between path-like variables (which identify core resources) and query-like variables (which are optional parameters). This will enable the MCP Inspector to allow resource browsing with only essential path variables filled, while treating query parameters as optional filters.

Motivation and Context

The MCP Inspector currently requires all URI template variables to be filled before allowing reading of resources from resource templates, which makes it difficult to explore available resources and understand what variables are needed. Some query parameters MAY be optional. This change enables better resource discovery by distinguishing between path-like variables (which identify the core resource) and query-like variables (which are optional filters/parameters).

This addresses the need for more intuitive resource browsing in MCP Inspector, where users should be able to access resources with only essential path variables while treating query parameters as optional enhancements.

How Has This Been Tested?

• Added comprehensive test suite covering all RFC 6570 expansion operators
• Tests for edge cases (templates with no variables, only path variables, only query variables)
• Validated correct classification of mixed templates with both path and query variables
• All existing tests continue to pass, ensuring backward compatibility
• Tested with real MCP resource templates like database://users/{id}{?limit,offset}

Breaking Changes

No breaking changes. This is a purely additive feature that maintains full backward compatibility with existing code.

Types of changes

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• 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

Implementation Details:

• pathVariableNames: Returns variables from path-like expansions ("", "+", "#", ".", "/" operators)
• queryVariableNames: Returns variables from query-like expansions ("?", "&" operators)
• Classification based on RFC 6570 expansion operators, not semantic assumptions
• Maintains existing variableNames getter for full compatibility

Use Case Example:

const template = new UriTemplate("database://users/{id}/posts{?limit,offset}");
template.pathVariableNames;  // ["id"] - structurally required
template.queryVariableNames; // ["limit", "offset"] - optional parameters

This change will enable MCP Inspector to allow browsing database://users/123/posts without requiring query parameters, while still showing what optional filters are available.

RFC 6570 Compliance:

• Path-like variables affect URI structure when omitted
• Query-like variables only affect query parameters when omitted
• Both types are technically optional per RFC 6570, but have different structural implications
• Implementation follows RFC 6570 expansion mechanics precisely