fix(ci): use bun.lock in setup-bun cache key

[SergioChan]

Issue for this PR

Closes #16289

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

• updates .github/actions/setup-bun/action.yml to hash bun.lock instead of bun.lockb
• aligns the cache key with the current Bun lockfile name
• prevents stale cache misses caused by hashing a deprecated lockfile path

How did you verify your code works?

• confirmed the repository lockfile exists (bun.lock)
• verified the setup-bun action now references hashFiles('**/bun.lock')

Screenshots / recordings

Not a UI change.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

⚠️ Potential Duplicate Found

PR #16291: "fix(ci): use bun.lock as caching key instead of deprecated bun.lockb"
#16291

Why they're related:

• Both PRs address the same issue (setup-bun action uses incorrect cache key #16289) - updating the setup-bun cache key from bun.lockb to bun.lock
• Both fix the same problem: preventing stale cache misses caused by hashing a deprecated lockfile
• PR fix(ci): use bun.lock as caching key instead of deprecated bun.lockb #16291 appears to be an earlier or concurrent PR that accomplishes the exact same fix

Recommendation: Check if PR #16291 is already merged or in progress before proceeding with PR #16364.

[SergioChan]

Closing this as duplicate of #16291, which is already open for the same issue (#16289).