feat(jans-auth-server): allow invoke consent script by acr

[yuriyz]

Description

Currently it's invoked based on client configuration. However it shouldn't be problem to introduce new AS configuration property and invoke it based on acr if needed. For example

1. acr1 - consentScript1
2. acr2 - consentScript2
...
n. acrN - consentScriptN

Test cases and code coverage

• Write unit test to cover added/changed code
• Update integration tests to cover added/changed code
• documenation

[yuriyz]

From #10686 (comment)

What if we add another configuration property that has mapping acr to consent flow like this

agama_io.jans.authn.sms - io.jans.consent.A
agama_io.jans.authn.fido2 - io.jans.consent.B

Algorithm is :

1. AS got authorization request with acr_values=agama_io.jans.authn.sms
2. io.jans.authn.sms is run
3. AS identifies AgamaConsentBridge.py by configuration and also read another configuration property mapping and sets into session with consent_flow=io.jans.consent.A (it should be possible to load with context.getSessionAttributes().get("consent_flow")).

It means we will need two additional configuration mappings.