Feat: EligibilityVerifier custom text

[angela-tran]

Closes #319

[thekaveman]

Before we merge this, we have to update the fixture file(s) in dev

[thekaveman]

Can you please rename the fields I had added previously, to line up with the new ones you're adding (which I like better):

• form_sub_pattern (instead of regex)
• form_name_max_length

[thekaveman]

One more thing too - this is going to run migrations and create the fields, but the fixtures aren't updated to contain the new data. I updated the ticket with a new task for this.

[angela-tran]

Can you please rename the fields I had added previously, to line up with the new ones you're adding (which I like better):

* `form_sub_pattern` (instead of `regex`)

* `form_name_max_length`

I like that better too. Made this change in 7ed9492.

Note that I also reordered the fields in the model definition and fixtures to group them better. I left the order alone in the migration code to keep my changes minimal.

[angela-tran]

One more thing too - this is going to run migrations and create the fields, but the fixtures aren't updated to contain the new data. I updated the ticket with a new task for this.

Made this change in 984bf73. Some notes:

• I copied over existing msgids that correspond to the new fields. I imagine we'll rename some of these msgids in Update eligibility verification form to use dynamic data #324, namely the ones that have .index in their msgid but will be a part of the instructions page.
• I am also leaving it up to Django form to capture user's EligibilityVerifier selection #322 and Update eligibility verification form to use dynamic data #324 to add new PO file entries for selection_label/selection_label_description and form_sub_placeholder/form_name_placeholder, respectively.

[angela-tran]

Some open questions came up when I was looking at the PO entries. We could resolve them either as a part of this PR or as separate tickets/PRs. I noted the questions in the ticket (#319).

[angela-tran]

@thekaveman I updated the description in #319 and made those changes. This is ready for re-review 🔍

[thekaveman]

@angela-tran Looking at this again 👀

[thekaveman]

This is great!

I cleaned the compiled language files and rebuilt my local database; no reported errors, the migrations run, fixtures are imported, and language files compiled:

calitp@93063145f6a8  ~/app (feat/verifier-custom-text)
$ rm django.db 

calitp@93063145f6a8  ~/app (feat/verifier-custom-text)
$ rm benefits/locale/**/*.mo

calitp@93063145f6a8  ~/app (feat/verifier-custom-text)
$ bin/init.sh 
[21/Mar/2022 23:38:46] DEBUG benefits.core.urls:41 Register path converter: TransitAgencyPathConverter
[21/Mar/2022 23:38:46] DEBUG benefits.urls:34 Skip url registrations for admin
Operations to perform:
  Apply all migrations: core, sessions
Running migrations:
  Applying core.0001_initial... OK
  Applying sessions.0001_initial... OK
[21/Mar/2022 23:38:47] DEBUG benefits.core.urls:41 Register path converter: TransitAgencyPathConverter
[21/Mar/2022 23:38:47] DEBUG benefits.urls:34 Skip url registrations for admin
Installed 9 object(s) from 5 fixture(s)
superuser: Django not configured for Admin access
processing file django.po in /home/calitp/app/benefits/locale/en/LC_MESSAGES
processing file django.po in /home/calitp/app/benefits/locale/es/LC_MESSAGES

Launching the local app with F5 I can successfully verify a test user: