Install and use the correct node version when starting Next Build.

[timcosgrove]

Description

This corrects an issue where the Next Build server would not start up correctly when a CMS Tugboat instance is stood up. The underlying issue was our not using the correct Node.js version for Next Build on Tugboat when we upgraded Next Build from v16 to v18. This corrects that and will ensure that Next Build on CMS Tugboat always uses the correct version.

Relates to #20507

Testing done

Visited the Next Build site on the CMS Tugboat instance connected to this PR: https://next-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov/pittsburgh-health-care/stories/

Screenshots

QA steps

1. Go to the Tugboat dashboard for this PR: https://tugboat.vfs.va.gov/6763201c5134c90adaad18ce
2. Rebuild the instance (Under 'Actions', under the title).
3. Once the instance is rebuilt, visit https://next-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov/ . This should be a VA.gov 404 page; this is normal, as Next Build does not build the homepage.
4. Visit https://next-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov/pittsburgh-health-care/stories/ . The page should load with data.

Note that there are missing images in the header and footer of these pages. This is a problem that will need to be corrected in Next-Build; #20520 is open to work on that.

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• pinned all affected GitHub Actions at a specific commit by SHA?
• reviewed the source code of the action at the commit you are pinning?
• confirmed that no GitHub security measures are being bypassed?
• checked for any injection of user content into protected contexts?
• reviewed Security hardening for GitHub Actions?
• reviewed GitHub Workflows?

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[timcosgrove]

This is the only substantive change here. Next.js must be built before the server can be started; that is changed here. Also, the & puts this task in the background; otherwise, it starts the server but then never continues because composer va:next:start holds the 'command line'.

[timcosgrove]

Nearly all changes in this file are spacing/autoformatting; the actual change is marked below.

[va-cms-bot]

Tugboat has finished building the preview for this pull request!

Links:

• https://pr20132-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov
• https://cms-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov
• https://web-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov
• https://storybook-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov
• https://next-mtm8unctm8wvkyykpkapajohgwrnkju8.ci.cms.va.gov

Dashboard:

• https://tugboat.vfs.va.gov/6763201c5134c90adaad18ce

[va-cms-bot]

Cypress Accessibility Violations

/test-data-aut

ID: button-name
Impact: critical
Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT
Description: Ensure buttons have discernible text
Help: Buttons must have discernible text
Nodes:

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Page introduction' field" data-proofing-help="Add an introduction that helps visitors understand if information on the page is relevant to them."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: .field--name-field-intro-text-limited-html > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Generate a table of contents from major headings' field" data-proofing-help="By checking this box, all h2's below this point on the page will be linked with with anchor links. This helps users navigate content on very long pages. Do not check this box unless there is at least 2 h2's on the page.">
  Impact: critical
  Target: .field--name-field-table-of-contents-boolean > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Main content' field" data-proofing-help="The main body of the page, which appears below the featured content."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: button[data-proofing-help-title="About 'Main content' field"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

[edmund-dunn]

Nice work! Everything works as expected!