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
  • Concisely describe Mainline and TrackReleaseBranches version strategies
• Improve listing of version strategies on "Configuration" docs page
  • Replace TrunkBased strategy listing with Mainline
• 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]

@HHobeck can you check the changes for the documentations?

[HHobeck]

@HHobeck can you check the changes for the documentations?

Yes, I try to do the review tomorrow.

[HHobeck]

May I ask you to document this? #4248

[selfdocumentingcode]

May I ask you to document this? #4248

Sure! Check my latest commits.

[arturcic]

@HHobeck if there are no additional changes that need to be added, please merge this PR

[HHobeck]

@HHobeck if there are no additional changes that need to be added, please merge this PR

Not sure why just the auto merge option is shown