Draft: Add LnR workflow specifically for Internal requests requesting a SaaS trial to protect customers during debook/rebook situations

Why is this change being made?

Currently there is no workflow that covers the situation where sales request a trial to keep the customer namespace on a plan while their subscription is cancelled and rebooked. This occurs commonly when contracts are being reset.

DealDesk seems to now be actively telling account owners when they will be debook/rebooking subscriptions and advising them to request a trial.

Note: A new Internal request form to alert us of this situation should be used to avoid a 'normal' extension being applied to a subscription which would drop to free when the underlying subscription is cancelled. (a soon to be done MR).

The process discussed in this slack thread I followed this process through a couple of situations earlier this year - would like confirmation from others on the L&R team to confirm that this is the best way to approach the situation where the customer has/has not had a trial on the namespace previously.

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.

---