VACMS-16288 use generated assets for next preview server

[tjheffner]

Description

Relates to #16288. (or closes?)

next-build needs the assets from vets-website, cms already requests a full content release, let's re-use those assets to save a little bit of time.

Not able to re-use the vets-website built from content-build, issues with symlinks & timing. Easiest approach for now is to build vets-website separately solely for next-build's use.

Testing done

• tried different combinations of yarn dev and yarn start with symlinks from vets-website directories. Ultimately, needed to build and install vets-website at the tugboat root (similar to next-build) and symlink from there. In this way, we can ensure that assets are available for next-build preview immediately without failure.

QA steps

• enable the next build feature flag
• visit a story page
• preview hopefully renders quicker than it does, with all correct assets in place

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

[tjheffner]

Noting that attempting to symlink to the vets-website installed inside vendor seemed to have issues either creating the symlink or building vets-website later as part of content-build.

Installing & symlinking to a different directory entirely had no issues, the assets are immediately present for the next-build server.

[tjheffner]

Noting that the Rebuild Tugboat Preview / Rebuild Tugboat Preview (pull_request) Failing after 6s check is a false alarm for this PR, as I needed to manually rebuild the tugboat preview to test changes inside the init: block. All other checks are passing, which is expected.

[ndouglas]

Thank you again for discussing the approach with me 🙂