Change Sauce check-my-repo publish to a branch

[discombobulateme]

Expected Behavior

check-my-repo should be a model project, clean and ready to be forked. However, since it is also used by Sauce, it is causing our results to be wrong, since parameters that should be default such as code-of-conduct are not editable. To solve this problem it is proposed that the site published at open source.saucelabs.com/check-my-repo comes from a branch instead of the main repo.

In this issue we expect to deliver 2 different results:

1. transform the main branch into a clean and most comprehensive repository possible to be forked
2. prepare a repository for Sauce Labs OSPO that will serve Sauce Labs OSPO. For that, either create nd deploy from a branch or use repolinter to check default organization documents https://github.com/saucelabs/.github

[discombobulateme]

First part of this issue, have a more comprehensive repository, has solved at: #164

[discombobulateme]

As a provisory patch, added a new action to deploy from sauce-ospo branch, where several rules where edite to match Sauce's .github Community Health Default Files https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file