VACMS-0000: Resync stray config changes to code

[chri5tia]

Description

No ticket.

This PR resyncs some straggling database changes back to code. Most of them appear to just be weight changes/re-order of fields and data elements.

Testing done

Some in-browser functional testing.

Screenshots

n/a

QA steps

Take a look at the code syncs and make sure nothing seems amiss. No functionality of the site should have changed.

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[swirtSJW]

These changes all make sense. Largely outputing format changes. All good.

[swirtSJW]

Thanks for taking this on @chri5tia. That is a big help.