Add support for NestJS v11 and fix security vulnerabilities

[diegofer25]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

The library currently only supports NestJS versions 6-10, and there were 14 security vulnerabilities in dependencies. Additionally, the AzureHttpRouter class was missing required methods (getHeader and appendHeader) that were added to the AbstractHttpAdapter interface in newer NestJS versions.

What is the new behavior?

• NestJS v11 Support: Added official support for NestJS v11 by updating peer dependencies to include ^11.0.0
• Security Fixes: Resolved all 14 vulnerabilities (1 low, 5 moderate, 7 high, 1 critical) by updating dependencies
• Compatibility: Added missing getHeader and appendHeader methods to AzureHttpRouter class to maintain compatibility with updated NestJS interfaces
• Documentation: Updated agents.md to reflect the new version support range (v6-11)
• Testing: Verified full compatibility with NestJS v11.1.5 - all builds and tests pass successfully

Key Changes:

• Updated @nestjs/common and @nestjs/core peer dependencies to support ^11.0.0
• Updated dev dependencies to NestJS v11.1.5 for testing
• Fixed security vulnerabilities in Babel, @octokit, cross-spawn, ip, path-to-regexp, semver, and brace-expansion packages
• Implemented missing HTTP adapter methods for full NestJS v11 compatibility

Does this PR introduce a breaking change?

• Yes
• No

This PR is fully backward compatible. Existing applications using NestJS v6-10 will continue to work without any changes, while new applications can now use NestJS v11.

Other information

• Tested Versions: Confirmed compatibility with NestJS v11.1.5
• Security: All vulnerabilities have been resolved (0 vulnerabilities after fixes)
• Performance: No performance impact - maintains existing functionality while adding forward compatibility
• Migration: No migration required for existing users; NestJS v11 users can now upgrade safely

This enhancement allows users to take advantage of the latest NestJS features while maintaining the same Azure Functions integration experience.