Add scope strategy allowing different separator for prefixes, resources and verbs

[zoop-btc]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

I want to implement a scope strategy in my Application which allows for different separators between dynamic scopes, resources & verbs. Right now this is the closest we can get.

Describe your ideal solution

The ideal solution would be to follow this recommendation.
For summary we'd have these things to check for:

• - for prefix scopes so budget-* matches budget-400 and budget-5
• : to separate resources so right now hydra.clients would be replaced by hydra:clients
• . for specifying the permission/verb hydra:clients.read for example

Workarounds or alternatives

I would have to use . as separator exclusively, making it hard to differentiate between prefix, resource and verb in my application.
Or I'd need to compile my own fosite & hydra with my custom scope strategy which adds significant complexity to my deployment pipeline & maintenance.

Version

latest

Additional Context

I'd also be happy if I could just use the prefix scopes and continue to use . as resource as well as verb separator.

[zoop-btc]

it looks like you were amenable to such an implementation here, I will create a fosite PR for this then

opened draft PR here - feedback welcome