VACMS-16853: next build branches ftw

[alexfinnarn]

Description

closes #16853

Testing done

• Updated some tests for git information/API/frontend.
• Manually tested locally by running script.
• Need to test on Tugboat with this PR.

Screenshots

Content release form when you can trigger a build.

Content release form when build is running with a link to the build log.

QA steps

1. Log in and go to "/admin/content/deploy/next"
   • Confirm you can select versions of next-build and vets-website from git references
   • Confirm there is no build in progress
   • No request or lock files should exist
   • The versions for next-build and vets-website should be "__default"
2. Submit the form with two branches chosen for next-build and vets-website
   • Confirm that a build request file exists.
   • No build should have started yet so no lock file should exist.
   • The versions for next-build and vets-website should be reported as what you selected.
3. Refresh the page a few times until the background process kicks off from reading the build request file.
   • Confirm that the form fields are locked during the build.
   • Confirm you can view the build log file and it is adding data until the build finishes.
4. Refresh the form page after the build is complete
   • Confirm the disabled fields are no longer disabled.
   • View the log to see that the build finished. It might have an error, but that will be addressed in future tickets.

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

[tjheffner]

is there a reason this is relative vs the rest of the roots above? /var/www/cms/next ?

[alexfinnarn]

No reason, just I knew that next was one directory above the docroot. I thought the right location for next was /var/www/html/next in ddev, but I could have gotten the wrong place if the repo is included other places. I don't see /var/www/cms locally, just /var/www/html/web which is a symlink to docroot/vendor/va-gov/content-build. But since this is a default settings file, I'm not sure these values carry through other overrides. They do get overriden in other settings files.

[tjheffner]

if they get overridden elsewhere i'm not too worried about it. /var/www/cms/ may even be leftover from when the project used lando before ddev. it just stuck out to me because it was noticeably different format than the lines above.

[edmund-dunn]

This looks good, nice and clean!!