Add clarification for scenarios in which Workday can be leveraged for internal transfers

Why is this change being made?

We have been receiving requests in the Development department to change team member's job titles to a new job family within the Development department to more accurately map to current scope of work (I.E. Backend Engineer to Fullstack Engineer). Currently, we state that all lateral transfers should go through Greenhouse reqs, but this does not work for this situation, as there are not open roles to move into, it is just a title change for existing team members.

I discussed a situation like the one outlined above recently with @gl-people-connect-team here, and we aligned that the most effective and efficient way to make the change was through Workday.

The MR adds clarification for scenarios in which Workday can be leveraged for internal transfers so we're consistent moving forward and so guidance is clear for the business.

cc @gl-peoplepartners for visibility on this and feedback (though I'm conscious this is likely more R&D-specific)

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.

---