Add authority bulk create (backend & frontend)

[mbklein]

Summary

Implement bulk creation of local authorities

Specific Changes in this PR

• Add /api/authority_records/bulk_create route for submission of CSV
• Add Bulk Add button to Local Authorities dashboard

Version bump required by the PR

See Semantic Versioning 2.0.0 for help discerning which is required.

• Patch
• Minor
• Major

Steps to Test

1. Create a CSV file with two columns (with headers): label and hint and several rows of new authorities. Feel free to include labels that already exist to test duplicate handling.
2. Log in as a user with access to the Local Authorities dashboard
3. Navigate to the Local Authorities dashboard
4. Click the Bulk Add button
5. Drag 'n' drop or click-to-select your CSV file.
6. Click Upload

The modal popup should close, and your browser should download a CSV file containing the results (labels, hints, IDs, and an indication of whether the line item was created or if it was a dupe).

You can do a "bad data" test by:

• submitting a CSV file with too many columns or headers with the wrong names
• submitting a file that isn't a CSV at all

Bad data should cause a redirect right back to the local authorities page. Due to the nature of how this direct POST works, displaying an error message would take a lot more work that might not be worth it.

🚀 Deployment Notes

Note - if you check any of these boxes go to the (always open) main <- staging PR and add detailed notes and instructions to help out others who may end up deploying your changes to production

• Backward compatible API changes
  • Database Schema changes
  • GraphQL API
  • Elasticsearch API
  • Ingest Sheet
  • CSV metadata export/update API
  • Shared Links export API
• Backwards-incompatible API changes
  • Database Schema changes
  • GraphQL API
  • Elasticsearch API
  • Ingest Sheet
  • CSV metadata export/update API
  • Shared Links export API
  • New backend route
• Requires data migration
• Requires database triggers disabled during deployment/migration
• Requires reindex
• Terraform changes
  • Adds/requires new or changed Terraform variables
• Pipeline configuration changes (requires mix meadow.pipeline.setup run)
• Requires new variable added to miscellany
• Specific deployment synchronization instructions with other apps/API's
• Other specific instructions/tasks

Tested/Verified

• End users/stakeholders

[kdid]

@mbklein - I'm getting a 400 error. I did do a mix deps.get and a mix assets.install.

This is all I saw in the log:

module=Phoenix.Logger [debug] Processing with MeadowWeb.AuthorityRecordsController.bulk_create/2
  Parameters: %{}
  Pipelines: [:api]
module=Meadow.Accounts.User [debug] User ksd927 found in cache
module=Phoenix.Logger [debug] Converted error Phoenix.ActionClauseError to 400 response