chore(security): remove GitHub Actions caching to prevent cache poisoning

[abretonc7s]

Description

Context

This PR updates our GitHub Actions workflows to use artifacts instead of caching for better control over build outputs. The changes affect the lint-build-test.yml and publish-release.yml workflows.

Changes

• Removed cache: yarn configurations from all Node.js setup steps in lint-build-test.yml
• Updated publish-release.yml workflow to:
  • Replace caching mechanism with GitHub Artifacts for build outputs
  • Upgrade GitHub Actions to newer versions (checkout@v4, setup-node@v4)
  • Remove the npm publish dry-run step for a more streamlined release process
  • Implement proper artifact handling between jobs using upload-artifact@v4 and download-artifact@v4

Implementation Details

This change replaces the GitHub Actions caching mechanism with artifacts for managing build outputs between jobs. This provides more explicit control over how build artifacts are handled and transferred throughout the workflow.

Performance Considerations

Build times may slightly increase without caching, but the artifact implementation ensures efficient transfer of build outputs between jobs. We can monitor and optimize if needed.

Breaking Changes

None. This is an internal workflow change that doesn't affect the published packages or their consumers.

Testing Instructions

1. Create a test release to verify the complete workflow
2. Monitor build times to assess performance impact
3. Verify that build artifacts are properly transferred between the release and publish jobs

Related Issues

#3925 - Remove usage of GitHub action caching from critical workflows

[chakra-guy]

LGTM