VACMS-15155: Updates the naming schema for VBA, splits with NCA

[omahane]

Description

Relates to #15155

Testing done

Manually

Screenshots

QA steps

Set up QA Content Publisher as a VBA Editor

• As an admin, assign the following roles to QA Content Publisher
  • Content creator - VBA
  • Content publisher
• Assign the following Sections to QA Content Publisher
  • Cheyenne VA Regional Benefit Office

Test NCA URL

• As an admin (as we don't have an NCA role at present), publish an NCA facility currently in draft
• Confirm that the URL is following the previously established/not yet CAIA-approved naming schema

Test VBA URL

• As QA Content Publisher, publish a VBA facility currently in draft
• Confirm that the URL is following the CAIA-approved naming schema

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

[github-actions]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• pinned all affected GitHub Actions at a specific commit by SHA?
• reviewed the source code of the action at the commit you are pinning?
• confirmed that no GitHub security measures are being bypassed?
• checked for any injection of user content into protected contexts?
• reviewed Security hardening for GitHub Actions?
• reviewed GitHub Workflows?

[dsasser]

Changes look good and QA steps passed.

[davidmpickett]

QA passes

• Something I noticed that's not part of the ACs - the NCA Node view doesn't seem to have the VA URL slot in the right-hand column. Might be a backlog issue

VBA facility URLs update to correct format upon publishing

NCA facilities retain existing format upon publishing

[omahane]

@davidmpickett After a bit of digging around, I think that the reason NCA facility doesn't produce a link while VBA facility does has to do with this form (staging link posted because prod is being updated): https://staging.cms.va.gov/admin/config/content/exclusion-types-form