What is this change about?

New acceptance tests for the service credential binding rotations feature.

The first test creates one service binding for the test app / test service and records its guid. Then it creates a second binding (with the multiple strategy), restages the test app and ensures that the binding guid has changed. This validates the full "credential rotation" scenario.

The other tests create two service bindings for the test app / test service and then check the following actions:

1. cf service <service name> shows all bindings
2. cf unbind-service <app name> <service name> deletes all bindings
3. cf cleanup-outdated-service-bindings deletes the oldest binding

Please provide contextual information.

https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0040-service-binding-rotation.md

What version of cf-deployment have you run this cf-acceptance-test change against?

v54.14.0 (with cc.max_service_credential_bindings_per_app_service_instance set to 2)

Please check all that apply for this PR:

• introduces a new test --- Are you sure everyone should be running this test?
• changes an existing test
• requires an update to a CATs integration-config (new config option include_service_credential_binding_rotation, default is false)

Did you update the README as appropriate for this change?

• YES
• N/A

If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?

This is a new major CF feature, see RFC-0040.

How many more (or fewer) seconds of runtime will this change introduce to CATs?

Each test takes about 4 minutes to complete, so an additional of 12 minutes (if test suite is enabled).

What is the level of urgency for publishing this change?

• Urgent - unblocks current or future work
• Slightly Less than Urgent