Allow SM customers migrating to SaaS to request namespace squatting

Why is this change being made?

Recently an SM customer migrating to SaaS was rejected after requesting a namespace squatting (ZD ticket - internal link) in order to prepare a new group for their organization. IMHO that has happened due to inadequate wording in this workflow.

Discussion with another Support engineers (Pairing issue + followup ZD ticket - internal link), confirmed my understanding of the idea behind those criteria to be - that only paying customers should be allowed to ask for namespace squatting. Limiting that only to current SaaS customers might be too restrictive and would cause unnecessary actions for them (like creating a temporary SaaS group and renaming it later on). Mentioning this use-case explicitly should allow all Support engineers to understand the consideration criteria similarly. As an end-result it would contribute to customers' positive support experience.

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.

---