feat: 🎸 add scope support for marker function

[kekel87]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/jsverse/transloco/blob/master/CONTRIBUTING.md#commit
• 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
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

The marker function does not support scopes.
Some users use this workaround to get them, but it is induced by an unintentional implementation when extracting parameters.

Issue Number: #178, #132

What is the new behavior?

We can now indicate an optional scope in the marker function (or an alias).
marker is resolved independently of translate or selectTranslate.
Its typing has been updated accordingly.

Does this PR introduce a breaking change?

[X] Yes
[ ] No

Users using this workaround should delete it and update their marker function with scope.

Other information

@shaharkazaz following this discussion

[shaharkazaz]

@kekel87 Sorry it took me a while to get back
Would you like to reboot this?

[kekel87]

Hi, there,
Sorry a lot of work this summer and a new ongoing personal project 👶 😅 .
I'll see if I can find the time to rebase and resume this.
No guarantees.