Tugboat preview URLs (aliases) can contain human-readable identifiers

[acrollet]

User Story or Problem Statement

As a CMS user, I need to know which environment I am viewing, in order to know the context of the actions I wish to perform.

Acceptance Criteria

• Generated aliases can be configured for Tugboat previews, such as cms-wilmington-tyxuiused787878dfhuh.demo.cms.va.gov and web-wilmington-tyxuiused787878dfhuh.demo.cms.va.gov
• These aliases will show in the dropdown on Tubgboat UI not ready yet
• Aliases show in the GitHub comment on PRs
• Test to make sure that existing hostnames do not change
• Change management for VAMC upgrade team users and other product teams [@oksana-c ]

[ElijahLynn]

Scheduled meeting to discuss with @q0rban on Feb 16th for building in something to Tugboat directly.

[oksana-c]

linking to short-term solution for the QA URLs provided by @q0rban #4399

[jefflbrauer]

@oksana-c can we discuss the real need/priority for this? If its still a big pain point, we should break out "Change management for VAMC upgrade team users and other product teams" into its own story because that is a predecessor to this engineering work.

[ElijahLynn]

The 4th AC of this can't be met with the current PoC by James in #4399 as the URL will change.

Test to make sure that existing hostnames do not change

Need a decision on this to see if that is okay.

[oksana-c]

@jefflbrauer the change management AC cannot be broken out into its own story because it needs to be coordinated along w/ the rebuild of existing environments.
I agree w/ removal of Planned Work label, since we've learned that there is a blocker in changed URLs, which will make change management a bit more involved. Given other priorities, let's move this into next sprint as a stretch goal.

[jkalexander7]

Issue will be addressed in #8747