docs: Clarifying info about structured metadata, blooms

[JStickler]

What this PR does / why we need it:

Clarifying information about structured metadata after conversation with PM on Slack.

[loki-gh-app[bot]]

This PR must be merged before a backport PR will be created.

[loki-gh-app[bot]]

This PR must be merged before a backport PR will be created.

[loki-gh-app[bot]]

The backport to release-3.3.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-15058-to-release-3.3.x origin/release-3.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x e866c2ff570b1ea0c39abae4b31a519b307b6376

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-15058-to-release-3.3.x
# Create the PR body template
PR_BODY=$(gh pr view 15058 --json body --template 'Backport e866c2ff570b1ea0c39abae4b31a519b307b6376 from #15058{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'docs: Clarifying info about structured metadata, blooms (backport release-3.3.x)' --body-file - --label 'size/S' --label 'type/docs' --label 'backport' --base release-3.3.x --milestone release-3.3.x --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-15058-to-release-3.3.x

# Create a pull request where the `base` branch is `release-3.3.x` and the `compare`/`head` branch is `backport-15058-to-release-3.3.x`.

# Remove the local backport branch
git switch main
git branch -D backport-15058-to-release-3.3.x