[management] feat: Basic PocketID IDP integration

[jfrconley]

Describe your changes

Add support for integrating pocketid with netbird, allowing user information to be properly synced and displayed.
The goal is to bring support inline with integrations for other self hosted idp's with this implementation cribbing heavily from the existing keycloak and zitadel integrations.

This takes advantage of the PocketID REST API to do basic user data management.

Issue ticket number and link

This should fix the issue described in #3295, populating the email and name fields in the profile from data returned by PocketID

Stack

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)

By submitting this pull request, you confirm that you have read and agree to the terms of the Contributor License Agreement.

Documentation

Select exactly one:

• I added/updated documentation for this change
• Documentation is not needed for this change (explain why)

Docs PR URL (required if "docs added" is checked)

Paste the PR link from https://github.com/netbirdio/docs here:

netbirdio/docs#432

[CLAassistant]

All committers have signed the CLA.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jfrconley]

While implementing this, I did run into some confusion when looking at the zitadel and keycloak implementation. Is it intentional that updating the app metadata is optional? PocketID also does not have the direct concept of app metadata, though you could probably work something out using custom claims.