Tugboat Next.js server can be restarted via Composer command

[alexfinnarn]

Description

closes #17209 by adding commands to restart the next server after changing git branches.

Testing done

Tested on Tugboat with a test branch that makes the next-build footer red and switched between that branch and others.

Screenshots

test-red-footer branch on Tugboat

QA steps

1. Check that the preview server still works by going to the Tugboat URL for next, like https://next-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov/.
   • Validate that the homepage loads and the footer is the typical "VA blue" or whatever they call it.
   • Validate any tricky parts of next-build, if you know them. I am not aware of typical smoke tests.
2. Log into the CMS and head to "/admin/content/deploy/next".
3. Fill out and submit the next server restart form with test-red-footer branch for next-build version and something else for the vets-website version.
4. Wait a few seconds and refresh. Refresh again if the form fields are not disabled and the build has not started.
   • Validate that the form fields are disabled during the build.
   • Validate that the next-build.txt file link leads to a log file with data in it. The log should grow every time you refresh and end with ==> Done.
5. Refresh the tab on "/admin/content/deploy/next".
   • Validate that the form fields are no longer disabled.
6. Navigate back to the next preview server, a URL like https://next-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov/.
   • Validate that the homepage loads and the footer is now bright red.
   • Validate any tricky parts of next-build, if you know them. I am not aware of typical smoke tests.
7. (Bonus Points) For a real parlor trick, you can navigate back to "/admin/content/deploy/next" and choose a different next-build branch to restart the server with. You'd have to create another PR in next-build with noticeable changes, but just reporting that users should be able to keep rebuilding the same Tugboat preview with various branches, even if most will only choose a branch one time.

Note: This PR, department-of-veterans-affairs/next-build#451, should be deleted after testing.

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

[va-cms-bot]

Tugboat has finished building the preview for this pull request!

Links:

• https://pr17400-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov
• https://cms-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov
• https://web-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov
• https://storybook-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov
• https://next-suer27t71oqpgngyx21sblb9hukdweph.ci.cms.va.gov

Dashboard:

• https://tugboat.vfs.va.gov/65ef926d93412038830a4a05

[alexfinnarn]

I need to delete this comment but don't want to rebuild Tugboat before a review.

[alexfinnarn]

I am unsure if running in the background is needed but I think the script paused and didn't continue. However, output isn't logged this way so might need adjusting to get output in logs if desired.