📖 Update Branch-Protection admin and non-admin requirements

[gabibguti]

What kind of change does this PR introduce?

This PR introduces a docs update for Branch-Protection check. It updates:

• which branch protection settings are required using non-admin and admin tokens

• which branch protection setting is evaluated in which Tier

• how to setup a perfect branch protection score for GitHub repos

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

The docs say:

• admin token is required to verify some settings which are available using non-admin token
• the settings evaluated are distributed in a way for the Tier's when it's distributed in a different way

What is the new behavior (if this is a feature change)?**

Fixed the settings required for admin and non-admin tokens and the settings distribution by Tier. Also, added a FAQ question to help users to setup a perfect branch protection score for GitHub repos.

• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

NONE

Special notes for your reviewer

Does this PR introduce a user-facing change?

For user-facing changes, please add a concise, human-readable release note to
the release-note

(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

Update docs on Branch-Protection to fix the settings required when using admin and non-admin tokens and the settings distribution by Tier

[gabibguti]

Can I get some help to reference local images in the code docs?

[codecov]

Codecov Report

Merging #2772 (2e3c0cc) into main (87b1c4c) will decrease coverage by 5.48%.
The diff coverage is n/a.

❗ Current head 2e3c0cc differs from pull request most recent head 78b3987. Consider uploading reports for the commit 78b3987 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2772      +/-   ##
==========================================
- Coverage   66.24%   60.76%   -5.48%     
==========================================
  Files         168      168              
  Lines       12611    12611              
==========================================
- Hits         8354     7663     -691     
- Misses       3791     4532     +741     
+ Partials      466      416      -50     

[github-actions]

Stale pull request message

[gabibguti]

It may also be worth documenting how to make a token to check the admin settings, as I couldn't figure it out in the few minutes I spent experimenting (although perhaps some org settings are blocking me). I'll need to check with @laurentsimon

True, I agree would be a good documentation.

[gabibguti]

The current documentation on Authorization covers how to create the token:

scorecard/README.md

Line 231 in 87b1c4c

- [Create a classic GitHub personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-personal-access-token-classic).

This setting is enough to run branch protection settings as admin when it's for your own repositories. For organizations, I'm not sure. Since Scorecard docs main target seems to be usage for individual repos, I think we're good.

[spencerschrock]

Thanks