🌱 Use rulesets if one exists when classic branch protection rule is inaccessible

[trask]

What kind of change does this PR introduce?

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

What is the current behavior?

Currently, when a classic branch protection rule is inaccessible (no special github token provided to access it):

• When it's the default branch, it will see if there is a ruleset for the default branch and use it if one exists
• When it's not the default branch, it will error, and you won't get a score for Branch-Protection

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

These two behaviors match. In both cases, it will see if there is a ruleset for the branch and use it if one exists.

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

I didn't find any existing tests for this code (either the default or non-default branch case). I can introduce if you wish.

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.)

Branch-Protection check now falls back to using GitHub Rulesets for non-default branches when classic branch protection rules are inaccessible (e.g., when using fine-grained access tokens without admin permissions).

[codecov]

Codecov Report

❌ Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 69.59%. Comparing base (353ed60) to head (4e140f9).
⚠️ Report is 281 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4853      +/-   ##
==========================================
+ Coverage   66.80%   69.59%   +2.78%     
==========================================
  Files         230      251      +21     
  Lines       16602    15657     -945     
==========================================
- Hits        11091    10896     -195     
+ Misses       4808     3891     -917     
- Partials      703      870     +167     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[spencerschrock]

/scdiff generate Branch-Protection

[github-actions]

Here's a link to the scdiff run

[spencerschrock]

Thanks. I tested this on actions/checkout with a fine grained PAT and it fixed the check.

Note to self: We already had some code duplication between setup and query, and now there's even more. It would be nice to cleanup eventually