[1.x] Fixes Relying Party custom ID

[DarkGhostHunter]

Fixes #50

Because WebAuthn RP custom ID was always wrong, you will need to update your user credentials to conform with the RP ID being a domain rather than an URL.

This introduces three fixes:

• When a new Credential is created, it will save the RelyingParty ID verbatim if was manually set, or extract the domain from the APP_URL.
• When an old Credential is retrieved, it will parse the rp_id to correctly extract the domain from the URL.
• Credential Attestation has been modified to always compare the RP ID as domains, rather than URL.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b172112) 85.44% compared to head (a670676) 85.45%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## 1.x #65 +/- ## ============================================ + Coverage 85.44% 85.45% +0.01% - Complexity 373 375 +2 ============================================ Files 63 63 Lines 996 997 +1 ============================================ + Hits 851 852 +1 Misses 145 145 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[sonarcloud[bot]]

Quality Gate passed

Issues
1 New issue

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud