Next Build server does not run correctly on CMS Tugboat instances

[timcosgrove]

User Story or Problem Statement

Next Build server does not run correctly on CMS Tugboat instances.

Description or Additional Context

When a user creates a new CMS Tugboat instance, through a PR or otherwise, that instance attempts to start a Next Build server. However, this is currently failing. The Next Build domain (https://next- on any Tugboat instance) instead reports a 403.

There is a PR open with some exploratory work on the problem: #20132

Issues the PR attempts to address:

• across the board making sure that the correct node version is activated prior to executing commands
• removing starting up next build from .tugboat.yml since it is already handled in .tugboat/config.yml

Steps for Implementation

Acceptance Criteria

• When a CMS Tugboat instance is created, a Next Build instance should be started and it should be functional
• Users should be able to see CMS content at the Next Build domain URL
• If a user creates new content, that should be viewable at the Next Build domain URL.