Add CTST coverage for Days=0 lifecycle expiration

[delthas]

What does this PR do, and why do we need it?

Adds end-to-end (CTST) coverage for S3 lifecycle Expiration rules with Days=0 ("delete all matching objects as soon as backbeat runs"), and bumps the component images that ship the feature.

• Bumps solution/deps.yaml: backbeat 9.5.0-preview.1 → 9.5.0-preview.3 (BB-791), cloudserver 9.4.0-preview.2 → 9.4.0-preview.4 (CLDSRV-928, arsenal 8.5.6), pensieve-api 1.10.1 → 1.11.0-preview.1 (PSVAPI-128).
• Adds features/lifecycleExpiration.feature with two @PreMerge scenarios using the direct S3 PutBucketLifecycleConfiguration API:
  • non-versioned bucket + Expiration Days=0 → all objects deleted;
  • versioned bucket + Expiration Days=0 + NoncurrentVersionExpiration NoncurrentDays=0 → all versions and delete markers removed.
• Factors the shared lifecycle-config PUT-with-retry logic out of the transition workflow helper into putBucketLifecycleConfigurationWithRetry, and adds an addExpirationWorkflow helper.

Days=0 makes objects immediately eligible (backbeat lists with no BeforeDate), so the test needs no time-progression or one-day-earlier tricks and is not tagged @Flaky.

The backbeat index-skip heuristic (BB-779) is intentionally out of scope — it is not yet merged and is covered by backbeat unit tests, not e2e.

Which issue does this PR fix?

ZENKO-5314

Special notes for your reviewers:

The new scenarios follow tests/functional/ctst/HOW_TO_WRITE_TESTS.md: unique per-scenario buckets, external-state-only assertions (via ListObjectVersions), poll-based assertions (idempotent after waits), automatic teardown via the global After hook, and no @Flaky.

Issue: ZENKO-5314

[bert-e]

Hello delthas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers