If GitHub provider fails to complete the authorization code flow, it will reply with 200, without the actual access token, causing a confusing error when Quarkus OIDC attempts to verify this non-existent token via the UserInfo injection...

This PR adds a couple of checks to fail early and an extra check to check the confusing error