Backport of [OSS PATCH] VAULT-36896: add clear logs about auto reporting disabling and enabling, update the docs into release/1.20.x

[hc-github-team-secure-vault-core]

Backport

This PR is auto-generated from #31258 to be assessed for backporting due to the inclusion of the label backport/1.20.x.

The below text is copied from the body of the original PR.

---

Description

This PR is an OSS patch, please view the associated ENT PR here: https://github.com/hashicorp/vault-enterprise/pull/8444

What does this PR do?

This PR adds clearer logs on when the automated license utilization reporting is enabled and disabled. The PR correspondingly updates the docs. In addition, some logs from license exporter have been updated too, so the docs are updated on these logs.

Why is this PR needed?

This PR brings about the changes that remove the confusion that came about from an escalation from a customer that said the automated license reporting continues to be working even when disabled because they do no see the log activity: there is no reporting agent configured, skipping counts reporting. This is expected however, since the code has been updated after manual reporting has been enabled to work all the time, thus always creating an agent for census. So this message cannot be relied on to indicate that this feature is disabled. For more information, please check comments on this Jira ticket: https://hashicorp.atlassian.net/browse/VAULT-36896?focusedCommentId=764218

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.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

---

Overview of commits

• 6e4b361

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[aslamovamir]

Closing since @schavis will push these changes to this Vault version after migration of docs files to a separate repo.