Specify FCL policy for allocated engineers

Why is this change being made?

Previously the FCL policy did not consider allocations/resets, where an engineer is on loan to another team. That led to at least one circumstance where a group was subject to an FCL through work that one of the group's engineers was doing on behalf of another group through an engineering allocation. This was surprising to many people, who felt the more predictable policy would be that the group that owned the work would be subject to the FCL.

This adds a sentence to the FCL policy to clarify the policy in the case of allocations/resets, to specify what people seem to feel lis the more predictable policy.

Author Checklist

• Provided a concise title for the 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 change to the correct DRI(s)
  • 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 in 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.

---