Support hot-reloading for all configuration values

[aeneasr]

Preflight checklist

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

Describe your problem

Currently, many configuration values can not be changed on the fly. This is because in a lot of places, the configuration is set on struct / service initialization and can then never be changed afterwards.

A big problem here is that Ory Fosite ( https://github.com/ory/fosite ) is using a static config system (which can only be changed on initialization) and also provides most of the configuration options.

Describe your ideal solution

Ideally, all configuration values would be consumed as functions GetSomeValue() string and not as values c.SomeValue. We have established a pattern in Ory Kratos and other projects already. The main concept is that every function which requires a configuration value is calling the service locator to find the right config struct this.Config(ctx) to then call the required config value.

As part of this change and to support full contextualization, we need to:

1. [ ] Do away with any context.TODO() or context.Background() that are used in non-tests
2. [ ] Ensure we never call the config struct directly in the registry (remove any references to m.C)
3. [ ] Contextualize Fosite's config which will require API changes

Workarounds or alternatives

none

Version

master

Additional Context

Implementing this effectively implements full Contextualization.

[aeneasr]

For fosite the easiest way to do it would probably be to define an interface for https://github.com/ory/fosite/blob/master/compose/config.go#L33 and go from there

[aeneasr]

done