Update Google cloud billing data as Tier 1 data source

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Proposition to update Google Cloud Billing data from Tier 3 to Tier 1 data source:

As per the definition:

Tier 3:

• Any data, process or related service that would not result in a immediate business impact if unavailable for more than 5 working days\
• Affecting less then 5 business users

And:

Tier 1:

• Any data, process, or related service that would result in a $X or higher business impact if unavailable for 24 hours\
• Affecting more than 15 business users

source

The specifications of the Google Cloud Billing data are the following:

• Data, process, or related service that would result in a $X or higher business impact if available for 24 hours ✅
  • If the Billing data is missing during the Finance end of month closure, the risk is at the level of our monthly spend: about $X.
  • We want engineers to catch cost incidents as soon as possible. $X per day is understating the risk taken by not giving immediate feedback on Cloud costs to engineers.

cc: @sshackelford @rtaira @james.shen @cdeleon_gitlab @dvanrooijen2

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---