fix(bb-cron-job): grant scheduler role access to all computes

[ikenyal]

Problem

After #459, CronJob correctly targets its resolved Lambda compute. The Scheduler IAM role remains shared per stack, however, and only receives lambda:InvokeFunction for the first CronJob target. A later CronJob targeting a different resolved Lambda synthesizes a correct schedule target but lacks permission for EventBridge Scheduler to invoke it.

Issue #: N/A

Changes

• Track the Lambda ARNs already granted to the shared Scheduler role.
• Add one lambda:InvokeFunction grant for each distinct CronJob target compute while preserving the existing single shared role per stack.
• Add a synth regression test with default and scoped Lambda computes that verifies the shared Scheduler role policy includes both targets.
• Add a patch changeset for @aws-blocks/bb-cron-job.

Validation

• npm run build --workspace @aws-blocks/bb-cron-job
• npm test --workspace @aws-blocks/bb-cron-job (65 passing)
• npm run lint
• npm run lint:deps
• npx changeset status --since=origin/main
• git diff --check

Checklist

• PR description included
• Tests are changed or added
• Relevant documentation is changed or added (not applicable: this fixes internal IAM synthesis behavior without changing the public API)

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0ba429b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@aws-blocks/bb-cron-job	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR