Modifying LACA Product page to incorporate info on permissive open source license use

Why is this change being made?

This MR is being submitted as part of LACA Product efforts to update its guidance on using open source libraries (utilising the Blue Oak Council list) at GitLab, to make it easier for team members to determine when legal input is required to use an open source license. This MR will also move this guidance to live in the LACA handbook (rather than the ENG handbook), so that LACA Product team members can efficiently update, as needed.

A separate MR to update the outdated guidance which sits in the ENG handbook is also being submitted here.

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.

---