docs: consistently use "> v{version} and after"

[agilgur5]

Motivation

• some said "since" or "and above", while most said "and after"

  • "above" is a SemVer ref, whereas "after" is a date ref, so I think the latter is easier to interpret
    • nbd either way IMO, but be consistent

• some just had the version without saying "and after" or similar

  • it is clearer to say "and after"
  • and most have it, so be consistent

• some were missing the "v" in front of the version

  • again, be consistent
  • also the "v" does in fact matter for referencing tags (git or Docker / OCI)

• two were in the wrong place, above the heading instead of below the heading

  • both were from docs: Updated WorkflowTemplateRef on WFT and CWFT #3137, which added the sections, so was quick to figure out where they should be

Modifications

• consistently use "> v{version} and after" for version references in the docs
  • if they are for a new section, consistently place them immediately below the heading of the section
• fix doubled > on an empty line

misc changes that were right next to the versions:

• fix typo "The submit a" -> "Then submit a"
• use a material warning admonition instead of a unicode caution sign, similar to docs(install): use material admonition instead of unicode caution #12561
• link to official k8s docs regarding HA and multi-AZs
  • anti-affinity is not the only way to do this now, and topology spread constraints is perhaps a better / newer way of doing it
  • also, in general, prefer official docs links over blog posts

Verification

1. Searched all references in the docs/ directory with "> "
2. make docs passes