[DOCS] Add steps for fixing aliases and names in the CMS for term changes

[swirtSJW]

Description

Relates to this Slack thread

Testing done

Screenshots

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

As user facilities team member

• Validate that the step added to the ACs in this template match the steps that will one day be automated

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

[davidmpickett]

"If term is part of VA Service Taxonomy & the term name changes:"
Suggested for more specificity. This template is also used when updating an existing term without the term name changing so won't always apply."

[swirtSJW]

Great suggestion. I just update the PR.