chore(scorecard): remove yarn4 config

[dzemanov]

Hey, I just made a Pull Request!

Use repo default yarn which is 3.8.7.

Fixing error on publish here: https://github.com/redhat-developer/rhdh-plugins/actions/runs/18462220498/job/52596360667#logs

Usage Error: Invalid option schema: missing at least one property from "all", "recursive", "since", or "worktree"

Fixes

Fixes https://issues.redhat.com/browse/RHDHBUGS-2163

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or Updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)

[christoph-jerolimov]

Thanks! 🙏

Do this need a changeset to build a new version?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dzemanov]

@christoph-jerolimov I would suggest we temporarily merge #1679, so we can rerun failed action here: https://github.com/redhat-developer/rhdh-plugins/actions/runs/18462220498/job/52596360667.
Only package version bumps trigger a new release, and this is only workspace change. I don't recommend we artificially bump packages just to release scorecard.

[dzemanov]

@christoph-jerolimov I would suggest we temporarily merge #1679, so we can rerun failed action here: https://github.com/redhat-developer/rhdh-plugins/actions/runs/18462220498/job/52596360667. Only package version bumps trigger a new release, and this is only workspace change. I don't recommend we artificially bump packages just to release scorecard.

Now thinking about it, it wont work, retriggering will use the old action definition, so we will need to add changeset here.

[dzemanov]

We can run release workspace action and set 'Force release even if no changesets are present', thank you @AndrienkoAleksandr for suggesting