Update to ACK runtime v0.56.0, code-generator v0.56.0

[ack-bot]

Update to ACK runtime v0.56.0, code-generator v0.56.0

---

• ACK code-generator v0.56.0 release notes
• ACK runtime v0.56.0 release notes

---

NOTE:
This PR increments the release version of service controller from v1.2.4 to v1.3.0

Once this PR is merged, release v1.3.0 will be automatically created for elasticache-controller

Please close this PR, if you do not want the new patch release for elasticache-controller

---

stdout for make build-controller:

building ack-generate ... ok.
==== building elasticache-controller ====
Copying common custom resource definitions into elasticache
Building Kubernetes API objects for elasticache
Generating deepcopy code for elasticache
Generating custom resource definitions for elasticache
Building service controller for elasticache
Running GO mod tidy
Generating RBAC manifests for elasticache
Running gofmt against generated code for elasticache
Updating additional GitHub repository maintenance files
==== building elasticache-controller release artifacts ====
Building release artifacts for elasticache-v1.3.0
Generating common custom resource definitions
Generating custom resource definitions for elasticache
Generating RBAC manifests for elasticache

---

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

To fix this problem, add an explicit permissions section to the workflow. This can be done at the root of the workflow file (which applies to all jobs unless overridden), or at the job level for the specific job. Placing it at the root is the best approach, ensuring no job can inadvertently escalate permissions unless intentionally specified. For most workflows, especially those that just call other workflows or perform read-only actions, the recommended minimum is contents: read. If the workflow requires write permissions for particular resources (e.g., for updating pull requests or issues), these should be added specifically. Here, as a minimal and safe starting point, add at the root:

permissions:
  contents: read

This should be inserted after the name (line 1), before the on: trigger, so that it clearly applies to all jobs.

[a-hilaly]

/lgtm

[a-hilaly]

/retest

[ack-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-hilaly, ack-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [a-hilaly]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ack-prow]

@ack-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
elasticache-verify-code-gen	3786baf	link	false	/test elasticache-verify-code-gen

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.