Update to ACK runtime v0.54.1, code-generator v0.54.0

[ack-bot]

Update to ACK runtime v0.54.1, code-generator v0.54.0

---

• ACK code-generator v0.54.0 release notes
• ACK runtime v0.54.1 release notes

---

NOTE:
This PR increments the release version of service controller from v1.1.2 to v1.1.3

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

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

---

stdout for make build-controller:

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

---

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

To address the issue, we should add a permissions block at the workflow level in .github/workflows/postsubmit.yaml, with minimal required permissions. Since the reusable workflow is being called via uses:, and unless there is evidence that it requires write permissions, we should use the least privilege principle. Typically, for workflows with no obvious write operations (such as publishing to contents or writing to issues/pull-requests), contents: read is an appropriate default. If later analysis shows that write access is needed for some scopes, those can be added. The permissions block should be inserted at the root level immediately below the name and before any on/jobs blocks.

---

[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
s3-verify-code-gen	56d9b2a	link	false	/test s3-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.

[a-hilaly]

/lgtm

[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