Migrate to Express v5 routes

[Mut1aq]

add names to wildcards for middlewares

Description

In Express 5, wildcards must have names; i18n.module had middleware registeration for all routes, so a name must be used after the "*" character.

Linked Issues

Additional context

[msalafia]

Any update on this?

[thomasglachant]

The feature is already working for me, there's just a linter issue to fix to be merged.
@Mut1aq can you fix this?

[C10ne]

As both Fastify and Express now use the latest path-to-regexp package there's no need to have different formats.

Suggested change

	isNestMiddleware(consumer) && usingFastify(consumer) ? '(.*path)' : '*path',
	'*path'

[MelanieW97]

Migrating to express@5 routes would be wonderful. Looking forward to that.
I've just tried to update to nestjs@11 just to find out that nestjs-i18n breaks my application with nestjs@11.
The issue I got occurs in combination with app.setGlobalPrefix('prefix').

error: Unsupported route path: "/prefix/*". In previous versions, the symbols ?, , and + were used to denote optional or repeating path parameters. The latest version of "path-to-regexp" now requires the use of named parameters. For example, instead of using a route like /users/ to capture all routes starting with "/users", you should use /users/*path. For more details, refer to the migration guide.

Someone also opened up an issue regarding my problem right here:
#694 (comment)

[toonvanstrijp]

@Mut1aq woud it be possible to check whenever express v5 is used? Currently this would make a breaking change right?