feat: init hydra consent and bump versions

[jonasbadstuebner]

I wanted to include Hydra consent in Kratos and this is working, "but" I also bumped the versions up to v1.1.0.
The Hydra-Consent page is not implemented if you don't specify HYDRA_ADMIN_URL as Environment variable. So it's optional and does not/should not break existing implementations.

I copy-pasted a lot from the Hydra-native implementation, so if you want some comments to be removed or whatever, just let me know, we can easily do that.

It uses the ory-native UserConsentCard for rendering the consent page and falls back to the default ory logo if no specific logo_uri is given on the client.

Related Issue or Design Document

Fixes #224
Closes #225

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

Further comments

[Benehiko]

Hey @DrBu7cher

Thank you for the contribution! I have cherry-picked this PR to a new branch and removed the consent routes here #229.

I did this since we require this repository on the latest SDK version, but do not currently have the time to review the consent routes right now - unfortunately 😞.

I hope you understand
Your contributions will still be in the new PR since it was a cherry-pick :)

[jonasbadstuebner]

Hey, @Benehiko ,

I understand, this is totally up to you. I extended my fork to also cover including the email in the id_token, since I needed that for my Grafana to work.
I am actively using this consent page and it's working great, since it uses your native UserConsentCard and the same logic as your hydra-consent-example.

If any time in the future one would like to combine the two examples, maybe this PR can be looked at again. :)

Best regards and thank you!

[Benehiko]

I have merged the other PR, so just rebase here - there shouldn't be a lot of conflicts since they were from the same commits.

I think you can keep this PR open and we will review it once we get the time ;)

[davidspek]

@DrBu7cher @Benehiko Could one of you reopen this PR? I think it got closed in the process of rebasing because it caused there to be no changes. However, the commit that was created after the PR was closed does contain changes.