Clarification on how to get approval for pre-approved software

Why is this change being made?

When needed to get a license for pre-approved software, the process in the handbook is not clear.

After asking on slack with @aabbate, I got clarification that the form used for not pre-approved software should be use it in the same way.

• Ashley Abbate: yes, you will need to fill out the form
• Michelle Torres: even when those are pre-approved? The questions on the form looks like more for a software that was not part of the approval process
• Ashley Abbate: Filling out the form allows us to create an issue to obtain manager/budget approval.

This MR adds a clarification to ask to get the form filled.

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.
• 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
• 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.

---