ci(workflows): comments drift from the ruleset, the action-gh-release pin and the no-timed-context rule #2231

Is your feature request related to a problem? Please describe.
Some workflow comments have drifted:

• cron-vendor.yml has change-relative comments. "Install and Setup" says vendor is for packages "which all lacks since design: write down what belongs in the all extra, and why #910". "Commit changes" tells the fix(ci): Vendor Update bumps for a new const module but never commits it #1685 story: a new module "was bumped for but never committed". Under docs: #719-style prose sweep after the #1090–#1102 defect wave #1103's no-timed-context rule, they should state the current behaviour.
• In unit-tests.yml, the comment above required-checks lists the required contexts of ruleset 23497679 as Required checks passed plus the Compat Python legs. The ruleset also requires Lint (gh api repos/JarryShaw/PyPCAPKit/rulesets/23497679), as workflows.rst's table already says.
• Create Release pins softprops/action-gh-release at v3.0.3 (chore(deps): bump softprops/action-gh-release from 3.0.2 to 3.0.3 #1992). releasing.rst, the create-release.yml and cron-conda.yml comments, and the test_release_tags_the_run_sha_1634 docstrings still cite 3.0.2. The cited behaviour is the same in 3.0.3, since its src/github.ts changes only error handling. (releasing.rst's :631-647 anchor is handled in test(project): verbatim text pins block fixing change-relative and wrong prose #2228.)

Describe the solution you'd like

• State the current behaviour in both cron-vendor.yml comments, keeping the issue numbers as references.
• Add Lint from lint.yml to the required-checks comment.
• Cite 3.0.3, or no version at all. The :631-647 line citation and its BARE_ELSEWHERE pin are covered by test(project): verbatim text pins block fixing change-relative and wrong prose #2228.

Additional context
This is prose only.