docs (user_workloads/monitoring): standardise format of code blocks for consistency

[jforce]

What this PR does / why we need it:
I've started to improve the code block formatting, first starting with the section user_workloads/monitoring as a taster.

Which issue(s) this PR fixes *
Part of #896)

Special notes for your reviewer:
I've done this initial PR as I was unsure whether I should do one XL PR to cover everything or break things up - (I feel that XLs could maybe be inelegant). So looking for some guidance on that. I'm fine on either approach I just didn't want to impose initially. I feel a PR per each major docs section could work best.

I've built and tested these changes locally and all look good to me.

FYI - @aburdenthehand

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mhenriks for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubevirt-bot]

Hi @jforce. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.