✨ Add releasing workflow for semantic-release

[travi]

What kind of change does this PR introduce?

this is a follow up to #2964 to support semantic-release as a releasing tool in addition to a packaging tool. i assumed incorrectly that both were covered by identifying semantic-release as a packaging tool

(Is it a bug fix, feature, docs update, something else?)

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

What is the current behavior?

semantic-release is recognized as a packaging tool, but not as a releasing tool

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

semantic-release is recognized as both a packaging tool and a releasing tool

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

i was unable to find tests for other releasing tools, even by removing existing tools and checking for failing tests. i'm happy to add a test for this case, if desired, but would appreciate guidance from maintainers of a desired approach

Which issue(s) this PR fixes

related to #2929

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

:sparkles: Add releasing workflow for semantic-release

[codecov]

Codecov Report

Merging #2989 (4b78948) into main (d97d8ce) will increase coverage by 0.03%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2989      +/-   ##
==========================================
+ Coverage   53.50%   53.54%   +0.03%     
==========================================
  Files         161      161              
  Lines       12312    12321       +9     
==========================================
+ Hits         6588     6597       +9     
  Misses       5350     5350              
  Partials      374      374              

[spencerschrock]

For tests, we sometimes have tests at the check level, instead of raw or evaluation. We're working on getting more tests broken down into the various packages where the code is.

Based on existing tests, it should be relatively painless to add a "release workflow contents write semantic-release" (or similarly named) entry into the table here:

scorecard/checks/permissions_test.go

Lines 260 to 282 in 3d1c472

	{
	name: "release workflow contents write",
	filenames: []string{"./testdata/.github/workflows/github-workflow-permissions-contents-writes-release.yaml"},
	expected: scut.TestReturn{
	Error: nil,
	Score: checker.MaxResultScore,
	NumberOfWarn: 0,
	NumberOfInfo: 2,
	NumberOfDebug: 4,
	},
	},
	{
	name: "release workflow contents write",
	filenames: []string{"./testdata/.github/workflows/github-workflow-permissions-contents-writes-release-mvn-release.yaml"},
	expected: scut.TestReturn{
	Error: nil,
	Score: checker.MaxResultScore,
	NumberOfWarn: 0,
	NumberOfInfo: 2,
	NumberOfDebug: 4,
	},
	},
	{

[travi]

Based on existing tests, it should be relatively painless to add a "release workflow contents write semantic-release" (or similarly named) entry into the table here:

thanks for the quick feedback. i got a test added there. open to feedback if you'd like to see more than that added

[spencerschrock]

Thanks for adding the test