VACMS-15222: Unlock benefit taxonomy fields to content admins

[chri5tia]

Description

Relates to #15222

Releases the lock down of the Benefit Name and ID fields for during the staging process of that content.

Note: Non-admins do not right now have access to this form but I structured the code so that it will be easier to lock down in the future as well as ensure that those fields aren't exposed to non-admins should access be granted to them.

Testing done

Functional.

Screenshots

QA steps

1. Log in as a testcontentadmin and got to admin/structure/taxonomy/manage/va_benefits_taxonomy/add
2. • Make sure the Name field is editable
3. • Make sure the ID field is editable

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