docs: in-place removal of source block macros to fix docs build

[yaauie]

Release notes

[rn:skip]

What does this PR do?

Fixes the docs build.

TIL that [source] blocks are handled as subdocuments in asciidoc, and their ability to link to the outer doc that contains them is implementation-specific. While my local docs tools can resolve the references, the docs build was broken by them 😩

Why is it important/What is the impact to the user?

It removes a broken thing from the docs used by the combined LS docs build.

We will need to mutate the tag held in github for the versioned plugin reference to pick up this fix since it is sourcing from rubygems version number (which is less than ideal), but with net zero code changes on this pre-1.0 project I am comfortable with the ramifications.

Once merged, we will need to push a tag deletion to github:

git push --delete origin v0.1.0 

And then this will need to be re-tagged (preferably including a cryptographic signature).

git fetch origin git checkout ${PR_MERGE_COMMIT} git tag -s v0.10 git push origin v0.1.0 

[karenzone]

Thanks for the fix to source.

[karenzone]

@yaauie, thanks for the fix. Merging so that correct formatting is safely in place in plugin source.

Because this is a docs-only change in a pre-release version, I don't believe that the above gymnastics are necessary. Let's discuss.