Describe the bug
In version 2024.12.2, this change breaks creating OIDC providers: https://github.com/goauthentik/authentik/pull/12530/files#diff-edb5bfb3cd2d70bd3cc2cf6bcd3810b4ba46e58b53f56f7cda9605383f2ea7b0. The api/v3/core/transactional/applications/ and api/v3/providers/oauth2/ endpoints both expect jwt_federation_sources to be a list of UUIDs, but a list of slugs is passed to it instead, preventing the creation of a provider.

To Reproduce
Steps to reproduce the behavior:

1. Have an OIDC/Oauth source configured like Google
2. Use the new application wizard or provider to create an OIDC provider
3. The creation will fail, with an error in the console such as {"jwt_federation_sources":["“google” is not a valid UUID."]}

Expected behavior
Successful creation

Screenshots

Logs
Output of docker-compose logs or kubectl logs respectively

{"auth_via": "session", "domain_url": "authentik.nathanv.app", "event": "/api/v3/core/transactional/applications/", "host": "authentik.nathanv.app", "level": "info", "logger": "authentik.asgi", "method": "PUT", "pid": 44, "remote": "10.42.3.0", "request_id": "202fe6546ecd484eb53669938dee1e74", "runtime": 58, "schema_name": "public", "scheme": "https", "status": 400, "timestamp": "2025-01-12T20:29:33.464880", "user": "nathan", "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"}

Version and Deployment (please complete the following information):

• authentik version: 2024.12.2
• Deployment: helm

Additional context
None