Add versioned links to docs and examples for v0.9.0

[afrittoli]

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a new binary/image to the cmd dir, please update
  the release Task to build and release this image.

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

[vdemeester]

/lgtm
/hold

Waiting for the tag to be created (and release done 👼) ?

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

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

[afrittoli]

I was hoping to merge this first and do the release right afterwards.
That means that for a few minutes those links will be broken, but in future, if someone checks out the tag, the link to the docs is there in the README.

[vdemeester]

@afrittoli make sense 👼
/hold cancel

[bobcatfish]

I think this was worth a shot but i just got pinged by someone who tried to follow the docs link for 0.9.0 and was confused why it was broken, so I think in the future it might be better to merge this after the release and tag are created?

[bobcatfish]

Or make sure we do it simultaneously! (With a Tekton Task maybe? :D)

[vdemeester]

I think this was worth a shot but i just got pinged by someone who tried to follow the docs link for 0.9.0 and was confused why it was broken, so I think in the future it might be better to merge this after the release and tag are created?

Waw some people are quite quick then 🤔 To @afrittoli's point, "That means that for a few minutes those links will be broken, but in future, if someone checks out the tag, the link to the docs is there in the README.", I think this is worth merging before the release (aka having this commit in the release). Maybe we need to "automate" the commit in the release pipeline 👼