chore(instrumentation-nestjs): update nestjs supported versions

[anuraaga]

Which problem is this PR solving?

• README is not up-to-date with code

Short description of the changes

• Updates supported versions in nestjs README

#2685 added support for NestJS 11 and I can confirm the latest released artifact works fine with it, so this updates the README to reflect it. I wasn't sure if it's better to remove <YY for YY that don't exist yet or keep it to not "pre-support" new major versions, let me know which is better.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.45%. Comparing base (e88ca9d) to head (6d6d39b).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2790   +/-   ##
=======================================
  Coverage   89.45%   89.45%           
=======================================
  Files         174      174           
  Lines        8319     8319           
  Branches     1592     1592           
=======================================
  Hits         7442     7442           
  Misses        877      877           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.

[anuraaga]

@neilime Updated this and I think just accidentally forgot to update the readme. I understand the sentiment about maintenance but does it make sense to go ahead and merge this @david-luna?

[pichlermarc]

Thanks @anuraaga 🙂

#2685 added support for NestJS 11 and I can confirm the latest released artifact works fine with it, so this updates the README to reflect it. I wasn't sure if it's better to remove <YY for YY that don't exist yet or keep it to not "pre-support" new major versions, let me know which is better.

Not pre-supporting is better - we do this to avoid breaking end users on new major versions.