(docs) Add automatic generation of TOC content

[AdmiringWorm]

Description

This pull request adds a new GitHub Action workflow that will generate and push a new commit to the repository when it needs to update the TOC content for both the Readme.md and Contributing.md files.

Motivation and Context

To have a TOC available for the files, without the need for us to create the TOC content manually.

How Has this Been Tested?

1. Tested on my fork to ensure that it works as expected. See AdmiringWorm@312146b as what it will create for this PR.

Screenshot (if appropriate, usually isn't needed):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Migrated package (a package has been migrated from another repository)
• Documentation

Checklist:

• My code follows the code style of this repository.
• My change requires a change to documentation (this usually means the notes in the description of a package). (Will happen automatically)
• I have updated the documentation accordingly (this usually means the notes in the description of a package).
• I have updated the package description and it is less than 4000 characters.
• All files are up to date with the latest Contributing Guidelines
• The added/modified package passed install/uninstall in the chocolatey test environment.
• The changes only affect a single package (not including meta package).

Original Location

N/A

Related Issues

Loosely related to #1754

[AppVeyorBot]

✅ Package verification completed without issues. PR is now pending human review

[AppVeyorBot]

✅ Package verification completed without issues. PR is now pending human review

[pauby]

I'm happy to merge this @gep13 ?

[gep13]

LGTM!

[gep13]

@AdmiringWorm thanks for getting this added!

[AdmiringWorm]

nice, looks like it successfully updated the TOC as well: d4c4809

Wasn't sure who it would commit as though, but looks like @gep13 is the lucky winner 😆

[gep13]

@AdmiringWorm said...
Wasn't sure who it would commit as though, but looks like @gep13 is the lucky winner 😆

I spotted that it was me, but I suspect going forward it will be the person doing the commit/merge into the main branch?

[AdmiringWorm]

yeah, that is what I expect to happen at least