Improve documentation around version strategies

[selfdocumentingcode]

Description

• Improve listing of version strategies on "How it works" docs page
  • Update names to reflect recent code changes
  • Replace (incorrect) examples with a link to the main version strategies list
  • Use a stub for the TrackReleaseBranches description (working on updating this one as well)
• Improve listing of version strategies on "Configuration" docs page
  • Replace TrunkBased strategy listing with Mainline
  • Mark TrackReleaseBranches as unused since technically it is an allowed value even though it's a noop.
• Fix Edit Diagram link on "How it works" docs page
• Update docs\readme.me build instructions to use correct target name for docs preview

Related Issue

#4219

Motivation and Context

I'm trying to understand how GitVersion works and the documentation makes it difficult at times.

How Has This Been Tested?

I built and ran a preview of /docs locally.

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[arturcic]

• Remove unused file docs\input\docs\references\mdsource\configuration.source.md

This one is actually used, and we have tests that check the content of the configuration.md based on the configuration.source.md. See #4104

[arturcic]

This should be kept

[selfdocumentingcode]

I see. That feature is not mentioned anywhere in the readme file nor did any tests failed after removing it.

I will, of course, remove the change from the PR.
Thanks for pointing it out!

Edit: @arturcic I am right to assume that for this particular change I'm making to the configuration.md file, i.e. unrelated to the GitVersion workflows, I have to also make the same change in the configuration.source.md file in order for the change in configuration.md to not get reverted the next time the mkdocs.yml workflow runs?

[arturcic]

I see. That feature is not mentioned anywhere in the readme file nor did any tests failed after removing it.

I will, of course, remove the change from the PR.
Thanks for pointing it out!

Edit: @arturcic I am right to assume that for this particular change I'm making to the configuration.md file, i.e. unrelated to the GitVersion workflows, I have to also make the same change in the configuration.source.md file in order for the change in configuration.md to not get reverted the next time the mkdocs.yml workflow runs?

Yes, please update the source file instead, as the configuration.md is updated from the source

[arturcic]

Please revert this change

[arturcic]

can you also include the details for MarkdownSnippets that converts the *.source.md into *.md files in this readme?
This tool is used to embed some files into md files

https://github.com/GitTools/GitVersion/blob/main/.github/workflows/mkdocs.yml#L24-L28