Refactor: AuthProvider to ClaimsProvider

[angela-tran]

Closes #2233 - see Acceptance Criteria on that ticket.

Testing locally

1. Checkout the main branch
2. Make sure your local_fixtures.json (or whatever fixture you are using) has an AuthProvider and an EligiblityVerifier that has a foreign key reference to that auth provider
3. Run bin/reset_db.sh (now your local DB mirrors the structure of the dev environment)
4. Checkout this PR's branch
5. Run bin/init.sh (running this PR's migration on top of existing DB structure)

• For all EligibilityVerifiers that with a reference to an AuthProvider, confirm those references were maintained, only now the field is called "Claims provider" in the admin interface, claims_provider in the database
• Confirm the Can X auth provider permissions are removed from the database
• Confirm the Can X claims provider permissions are added to the database
• Confirm the Cal-ITP group has Can [view|change] claims provider permissions
• Flows using claims from IdG should still work

[github-actions]

Preview url: https://benefits-2256--cal-itp-previews.netlify.app

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
benefits/core
admin.py
context_processors.py
middleware.py
models.py
benefits/eligibility
verify.py
views.py
benefits/enrollment
views.py
benefits/oauth
analytics.py
middleware.py
views.py
Project Total

This report was generated by python-coverage-comment-action

[angela-tran]

Ready for review

[angela-tran]

Not sure if this one (authentication providers) needs to be updated and/or what the right wording would be.

benefits/docs/README.md

Line 41 in 58abd80

`benefits` is a [Django 5][django] web application. The application talks to one or more [Eligibility Verification APIs](https://docs.calitp.org/eligibility-api/specification) or authentication providers. These APIs and the application itself are

[thekaveman]

Not sure if this one (authentication providers) needs to be updated and/or what the right wording would be.

benefits/docs/README.md

Line 41 in 58abd80

`benefits` is a [Django 5][django] web application. The application talks to one or more [Eligibility Verification APIs](https://docs.calitp.org/eligibility-api/specification) or authentication providers. These APIs and the application itself are

I think claims providers here is fine?

[lalver1]

The code changes look good! These were verified:

• For all EligibilityVerifiers that with a reference to an AuthProvider, confirm those references were maintained, only now the field is called "Claims provider" in the admin interface, claims_provider in the database
• Confirm the Can X auth provider permissions are removed from the database
• Confirm the Can X claims provider permissions are added to the database
• Confirm the Cal-ITP group has Can [view|change] claims provider permissions
• Flows using claims from IdG should still work

Just saw a minor typo in oauth.md.

[lalver1]

Sorry, tiny typo, maybe change:

an ClaimsProvider

to

a ClaimsProvider

[angela-tran]

Thanks! Made that change in ee3df8ec

[thekaveman]

This looks great 👍 !!!

[angela-tran]

Thanks for the reviews!