chore(deps): bump path-to-regexp from 6.3.0 to 8.4.2

[jNullj]

Some work that needs to be done pointed at this comment
Links to a list of breaking changes for: v7, v8

[github-actions]

	Messages
📖	✨ Thanks for your contribution to Shields, @jNullj!

Generated by 🚫 dangerJS against 07c85ae

[jNullj]

A few new insights

1. There is simply too much regex, every pattern's enum is not supports.
2. Rewriting all routes is lots of work.
3. I looked at a potential replacement regexparam, seems to not be easy to work with as it also does not support regex operations we need.
4. Another alternative url-pattern is unmaintained for 9 years.
5. I looked into how this will effect our move to express as we might be able to use some of it's functionality, and surprised to learn that express uses path-to-regexp.

some alternatives to pattern enum might be:

1. Accepting any string as route and validating the enum in service.
2. Extracting pattern options at prepareRoute and recreate the regex with the options (also should effect getEnum function).

[jNullj]

to solve this issue i think we better present a new boilerplate for enums.
considering we want to move to express.js in the future and that enums in paths are removed by design i think we should use per-badge enum check.
we have over 20 services to change, i think its best to brake it down to seperate PR to slowly change the code-base so we can ublock this PR.

i will start out by updating docs so future badges will be added correctly and we have a clear plane.
then i will hit multiple PR to include services in small chunks so we actually make progress towards this and not just stay with a huge roadblock.