Update Realignment Process Details

Why is this change being made?

Updating the current Realignment process to optimize for 1) agility, 2) efficiency, and 3) ensuring SSOT.

Since this page was created we've created a lot of new types of realignments, streamlined our processes, and expanded many teams. With the significant shift across the company to prioritize AI, we will likely be seeing more Borrows, Rapid Actions, Realignments, etc., and we want to ensure we are set up to be able to move quickly in a compliant way.

The core changes reflected are:

1. Referring to the realignment bucket as "Team Alignment Changes" to incorporate all of the types of changes we now have documented, as opposed to bucketing everything as a realignment. Since this page was created we now also have Borrows, Rapid Actions, Engineering Allocations, etc.
2. Streamlining our process and adding in a few key steps and resources (I.E. Team Member Realignment template)
3. Incorporating team alignment change key guiding principles
4. Defining when Legal does/does not need to be involved
5. Separating "Team Alignment Change process" touchpoints that should occur regardless of the change type from the core permanent realignment process

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---