[Docs] prometheus.exporter.[blackbox, snmp] misc. fixes

[spartan0x117]

PR Description

(Hopefully) alleviates some confusion in the docs for prometheus.exporter.blackbox and prometheus.exporter.snmp derive the name attribute from the label of the block and is not a required argument to the block.

Which issue(s) this PR fixes

Related to #5163

Notes to the Reviewer

PR Checklist

• Documentation added

[clayton-cornell]

LGTM

[clayton-cornell]

@spartan0x117 Can we backport this to v0.34, v0.35, and v0.36 docs or is it something for next only?

[spartan0x117]

@clayton-cornell I hadn't thought about the backporting when batching these changes. The blackbox and snmp changes should be fine for all of those, but the cloudwatch exporter was added in v0.35.

Should I remove the cloudwatch changes from this PR and make it a separate one?

[clayton-cornell]

@spartan0x117 We can remove the cloudwatch and do it in a separate PR... or backport to all anyway. If we backport to v0.34 the backport will fail because it can't cherrypick into a file that doesn't exist. We could checkout the faield backprot to v0.34, delete cloudwatch, and then push it.

Either way the result will be the same. Cleanest is to strip out cloudwatch into its own PR.

[spartan0x117]

Makes sense! I backed out the cloudwatch changes and moved them to this PR: #5195

[grafanabot]

The backport to release-v0.34 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-5187-to-release-v0.34 origin/release-v0.34
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 31999c8224d3d6cbf848fa441e5862a03abd5837
# Push it to GitHub
git push --set-upstream origin backport-5187-to-release-v0.34
git switch main
# Remove the local backport branch
git branch -D backport-5187-to-release-v0.34

Then, create a pull request where the base branch is release-v0.34 and the compare/head branch is backport-5187-to-release-v0.34.

[grafanabot]

The backport to release-v0.35 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-5187-to-release-v0.35 origin/release-v0.35
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 31999c8224d3d6cbf848fa441e5862a03abd5837
# Push it to GitHub
git push --set-upstream origin backport-5187-to-release-v0.35
git switch main
# Remove the local backport branch
git branch -D backport-5187-to-release-v0.35

Then, create a pull request where the base branch is release-v0.35 and the compare/head branch is backport-5187-to-release-v0.35.

[grafanabot]

The backport to release-v0.36 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-5187-to-release-v0.36 origin/release-v0.36
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 31999c8224d3d6cbf848fa441e5862a03abd5837
# Push it to GitHub
git push --set-upstream origin backport-5187-to-release-v0.36
git switch main
# Remove the local backport branch
git branch -D backport-5187-to-release-v0.36

Then, create a pull request where the base branch is release-v0.36 and the compare/head branch is backport-5187-to-release-v0.36.