VACMS-17221: Restore field_intro_text

[omahane]

Description

Relates to #17221

Testing done

Manually

Screenshots

QA steps

Set up the editor

• Log in as an admin
• Assign the user QA Content Publisher to the following role:
  • Content creator - VBA
• Assign the user to the following section:
  • Cheyenne VA Regional Benefit Office

Test the preview

• Log in as QA Content Publisher
• Edit the Cheyenne VA Regional Benefit Office
• Publish the page

Release content

• Log in as an admin
• Go to Release Content
• Click Release Content
• After a 3 - 4 minutes, click View build log
• Confirm that the following doesn't appear in the logs, under Beginning GraphQL queries with parallelization at 15 requests...

Error with GetVbaFacility__slice1. Scroll up for the GraphQL query that has an error:

[
  {
    "message": "Cannot query field \"fieldIntroText\" on type \"NodeVbaFacility\".",
    "extensions": {
      "category": "graphql"
    },
    "locations": [
      {
        "line": 52,
        "column": 11
      }
    ]
  }
]

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.
• If there are field changes, front end output has been thoroughly checked.

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

[omahane]

Making this PR ready for review is blocked by an issue I identified on Slack.

[omahane]

I created another PR that doesn't have the VBA facility changes but all other up to the present. It still had the same issue:

I am going to change the QA to not wait for the Release Content to finish, only to see that the field-related error did not reappear.

[Becapa]

Looks good. QA steps pass without a GraphQL Error: