[FEAT]: Do not panic if getting SAML metadatdata fails

[Frederic Jahn]

Checklist

• I could not find a solution in the existing issues or docs.
• I agree to follow this project's Code of Conduct.

Description

Currently Hanko gets metadata for all SAML connections on startup and when a call to a metadata endpoint fails (e.g. http code > 400, wrong response body) Hanko won't start.

Describe your ideal solution

Hanko should show a warning in the logs when it fails to get SAML metadata, but should start anyway.

Workarounds or alternatives

No response

Hanko Version

v0.10.2

Additional Context

No response

[Stefan Jacobi]

So we want to ignore that provider after the warning?

[Frederic Jahn]

So we want to ignore that provider after the warning?

Yes