Update `Usage Data` to `Usage Reporting` within Handbook pages

Why is this change being made?

Per discussion, we are changing the project called "Usage Data" to "Usage Reporting" to better reflect the purpose, scope, and value that will be realized.

References:

1. E-group slack post
2. Commentary for reasoning as we want to target the customer-centric outcome: data (source) > statistics (action) > report (outcome). With Usage Report, we drive with what the customer achieves, and that might help change focus.

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.

---