Readme update action

[max-programming]

This PR adds a github action that runs a script to update examples in the README.md file based on the config.json and techs.json files

What has changed:

• A techs.json file containing key-value pairs of all techs in README
• A config.json file in each example
• A Github action to run on every PR and look for these changes
• A script that is called by the action to update the README

[colbyfayock]

do you think it would make sense to default to the lowercase version of the tech if it doesnt existi n the mapping?

say someone adds "angular" as the tech, could just list out "angular" or a title cased version

another idea is to throw an error if the tech doesn't exist to force it to create a match. on top of that, you can add a validation on Pull Request to make sure the tech exists in the list, if it doesnt, the person making the PR needs to add it to the list

[max-programming]

Yeah this makes sense, added these features in the latest commit

[colbyfayock]

nice one, i assume its tested, hard for me to test i would assume. do you think this should run on PR or commits to main? wondering if trying to add it on PR would make it messy commit-wise

[max-programming]

@colbyfayock I think it's better to comment on the PR as the everything will be merged along with the PR.
Plus we can track what was added and removed in the PR itself

Here's how the process looks like.
❌ It comments if no tech was added
✔️ it updates the readme when the tech is added

[max-programming]

The error details section is now changed to "Missing tech(s)" and it'll include names of techs that aren't added in techs.json file

[colbyfayock]

awesome thanks @max-programming we'll see how it goes 🙌

[max-programming]

@colbyfayock One thing I forgot to mention is that you have to enable this option in the repository settings

[colbyfayock]

already done! thanks

[bradgarropy]

@max-programming This may not be working properly during the checkout portion.

Check out this workflow error.

[max-programming]

@bradgarropy I'll fix this up and let you know ✌️

[max-programming]

Fixes at #193