Update build process, use GitHub workflows

[nyanhp]

Description

I did not test the publishing step, but the validation seemed to work. The module works as well, but it is still a bit like open heart surgery insofar as that we don't have integration tests :)

New: Develop branch gets pre-released on every commit (i.e. after pull requests), to release to prod:

• git switch develop
• git pull
• Update-ModuleManifest AutomatedLab.Common/AutomatedLab.Common.psd1 -ModuleVersion
• git add AutomatedLab.Common/AutomatedLab.Common.psd1
• git commit -m "Release prepared"
• git checkout master
• git pull
• git merge --squash develop
• git push
• git switch develop
• git push

I hope that process is bearable @raandree, otherwise I'm open to ideas :)

• [ ] - I have tested my changes.
• [ ] - I have updated CHANGELOG.md and added my change to the Unreleased section
• [ ] - The PR has a meaningful title.
• [ ] - I updated my fork/branch and have integrated all changes from AutomatedLab.common/develop before creating the PR.

Type of change

• [ ] Bug fix
• [x] New functionality
• [ ] Breaking change
• [ ] Documentation

How was the change tested?

🤡 Local builds, builds in my fork, did not test all cmdlets

[nyanhp]

@raandree any opinions?