Adding initial CI Data Partitioning weekly project plan.

Why is this change being made?

As a part of a new experiment for adding key Ops sub-project plans to our handbook, this MR has been created to start collaborating on what our tentative goals look like for upcoming weeks/milestones. Async weekly update issues will merely point to this project plan to show work that is being focused on so that we only have 1 SSOT.

Updates, additions, deletions are very welcomed here from all!

NOTE: This experiment is intended to highlight the direction but also to adjust as time goes on when needed. As weeks complete, a collapsible table will be created as an Archive so that the latest weeks are always at the top of the list but people can review past work from past weeks/milestones if needed.

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.

---