Remove potentially misleading part of automated reporting docs

[VioletHynes]

Description

This section of the docs implies a way for customers to use and ingest the automated reporting, which has confused customers. I think it's clearer if we simply remove it.

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[judithpatudith]

Hello, and thank you for the feedback!! Just so I understand the issue and know what to ask about, are we saying that it isn't possible for customers to ingest the automated reporting data?

These docs are standardized across all the products and went through a kind of extensive vetting process, so I'd like to run the proposed change past those stakeholders to make sure that we're ok removing this line for all the products. Sorry to add a little bit or red tape, and thanks for your patience!

[VioletHynes]

It's possible to ingest license utilization data (e.g. https://developer.hashicorp.com/vault/api-docs/system/internal-counters) but that's not tied to automated reporting. This section has been misleading and has confused customers in the field. Automated reporting turns on reporting Census data to HashiCorp, not other reporting solutions --- and it's not intended to be customer facing (this is the main thing that has confused customers).