feat(core): add declarative route rewrites support

[mag123c]

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: #15619

What is the new behavior?

This PR introduces a declarative route rewrite system that allows applications to configure route rewrites at the application level using the routeRewrites option in NestApplicationOptions.

Key Features:

• Declarative Configuration: Configure route rewrites through application options
• HTTP Method Support: Specify which HTTP methods to apply rewrites to (or all methods by default)
• Custom Status Codes: Configure redirect status codes (defaults to 301 Moved Permanently)
• Global Prefix Integration: Automatically handles global prefix in route paths
• Performance Optimized: Route rewrites are registered during application startup, not per-request

const app = await NestFactory.create(AppModule, {
  routeRewrites: [
    // Redirect all methods from old path to new path
    { from: '/old-api', to: '/new-api' },

    // Method-specific rewrite with custom status code
    {
      from: '/legacy-users',
      to: '/users',
      methods: RequestMethod.GET,
      statusCode: 302
    },

    // Multiple methods
    {
      from: '/old-posts',
      to: '/posts',
      methods: [RequestMethod.GET, RequestMethod.POST]
    }
  ]
});

Does this PR introduce a breaking change?

• Yes
• No

Other information

Added private readonly config: ApplicationConfig parameter to enable access to route rewrite configurations

[coveralls]

Pull Request Test Coverage Report for Build b27093d3-0731-40d7-a3ef-1924c859f223

Details

• 35 of 35 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.05%) to 88.779%

---

Totals
Change from base Build 87823697-4182-4d9a-8625-1cc37cfa7f74:	0.05%
Covered Lines:	7303
Relevant Lines:	8226

---

💛 - Coveralls

[kamilmysliwiec]

As I mentioned here #15619 (comment), there's really no need to introduce a new dedicated feature for this when we have a working API in place

[kamilmysliwiec]

Thanks for your contribution, though. Great work anyway!

[mag123c]

@kamilmysliwiec
While working on it, I kept wondering if I needed this 😄
Thanks for comment