Clean up metadata issues

[laritakr]

Story

Metadata yaml files were audited and edited to:

• Change dates to be single rather than multiple
• Add multiple: false on form when term is not multiple... form defaults to multiple and term defaults to singular.
• Remove unnecessary state & arkivo_checksum
• remove dc_access_rights, which shares the same predicate in fedora with access_rights. (the shared predicate means they do the same thing, and the term is not accessed except in indexing.)

Refs

• Valkyrie: Collection Metadata issues on existing collections #777
• Sort out metadata fields #822

Expected Behavior Before Changes

Many works types could be created but not edited.
Metadata single or multiple on form did not match production.

Expected Behavior After Changes

• All work types and collection can be created.
• All work types and collection can be edited.
• All fields with the exception of based_near location dropdown can be used.

Screenshots / Video

All work types and collection were tested, and can be both created and edited.

Notes

OER and ETD do not currently work. These come in via Hyku and are not used in Adventist, so they have not been adequately set up. At this point, they should be deactivated in all tenants to avoid any potential issues.