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.1.3 to v1.2.0

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

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

---

stdout for make build-controller:

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

---

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

To fix the issue, add an explicit permissions block to the workflow. Because the workflow calls a reusable workflow as its only job, the minimal and safest fix is to set a root-level permissions: block that restricts the GITHUB_TOKEN to the least privilege required. If you do not know the specific permissions required, you should start with contents: read (the most basic permission often needed to check out code or read repository contents); you can then adjust if more permissions are required. The explicit permissions: block should be inserted after the name: declaration and before jobs:, so it applies to all jobs by default. No imports or definitions are necessary in this YAML file.

[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

[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
mq-verify-code-gen	1aa4c6e	link	false	/test mq-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.