Fix Go duration parsing in kafkaCleaner test

[delthas]

Summary

The kafkaCleaner end-to-end test (features/zzz.kafkaCleaner.feature) reads
KafkaCleanerInterval from the Zenko CR's spec.kafkaCleaner.interval field,
which is a Go duration string (e.g. "1m"). The test used parseInt("1m") to
convert this to seconds, but parseInt stops at the first non-numeric character
and silently returned 1 instead of 60.

This caused the test to compute a timeout of ~60s (1 × 6000ms × 10) instead
of the intended ~600s (60 × 6000ms × 10), giving the kafkacleaner only one
cleaning cycle to process all topics rather than ten. Under normal conditions one
cycle was often enough, but when operator reconciliation triggered topic
recreation mid-run, the kafkacleaner needed several cycles to catch up — and the
test failed with:

AssertionError: Kafka cleaner did not clean the topics within the expected time

Fix

Replace parseInt with a parseDurationToSeconds utility that properly handles
Go-style duration strings — including compound durations ("2h45m"), fractional
values ("1.5s"), and all standard time units (ns, us/µs, ms, s, m, h).

For the current "1m" value, this correctly returns 60 seconds, restoring the
intended 10-cycle timeout window.

Issue: ZENKO-5218

[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

[SylvainSenechal]

Hey I'm approving just some thoughts :
This new helper function is kinda ugly and will probably only be used once,

• I was thinking we could almost just drop the "KafkaCleanerInterval" parameters and just give that function 300sec to timeout.
• If you do keep the parseDurationSeconds, consider a few documentation example of what "duration: string" => result this function would process

More importantly : In that codebaase, we have Zenko.yaml, and it's got the kafkaCleaner.interval set to 1m, considering that all the tests we've got probably don't produce that many messages (maybe a few hundreds), and that the issue was probably situation where that kafka cleaner would start a few seconds before the wrong 60sec timeout instead of 600sec that we had, I would suggest lowering the value, somewhere between 15s and 30

[delthas]

Hey I'm approving just some thoughts : This new helper function is kinda ugly and will probably only be used once,

* I was thinking we could almost just drop the "KafkaCleanerInterval" parameters and just give that function 300sec to timeout.

* If you do keep the parseDurationSeconds, consider a few documentation example of what "duration: string" => result this function would process

More importantly : In that codebaase, we have Zenko.yaml, and it's got the kafkaCleaner.interval set to 1m, considering that all the tests we've got probably don't produce that many messages (maybe a few hundreds), and that the issue was probably situation where that kafka cleaner would start a few seconds before the wrong 60sec timeout instead of 600sec that we had, I would suggest lowering the value, somewhere between 15s and 30

Right. Testing with 15s, timeout of 5 minutes. Let's see how it goes.

[bert-e]

Waiting for approval

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

• the author

• 2 peers

The following reviewers are expecting changes from the author, or must review again:

• @francoisferrand

[delthas]

* If you do keep the parseDurationSeconds, consider a few documentation example of what "duration: string" => result this function would process

Documented.

[bert-e]

Waiting for approval

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

• the author

• 2 peers

[delthas]

/approve

[bert-e]

Build failed

The build for commit did not succeed in branch bugfix/ZENKO-5218/fix-duration-parsing-kafkacleaner

The following options are set: approve

[bert-e]

Build failed

The build for commit did not succeed in branch bugfix/ZENKO-5218/fix-duration-parsing-kafkacleaner

The following options are set: approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/2.14

The following branches will NOT be impacted:

• development/2.10
• development/2.11
• development/2.12
• development/2.13
• development/2.5
• development/2.6
• development/2.7
• development/2.8
• development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

Queue build failed

The corresponding build for the queue failed:

• Checkout the status page.
• Identify the failing build and review the logs.
• If no issue is found, re-run the build.
• If an issue is identified, checkout the steps below to remove
  the pull request from the queue for further analysis and maybe rebase/merge.

Remove the pull request from the queue

• Add a /wait comment on this pull request.
• Click on login on the status page.
• Go into the manage page.
• Find the option called Rebuild the queue and click on it.
  Bert-E will loop again on all pull requests to put the valid ones
  in the queue again, while skipping the one with the /wait comment.
• Wait for the new queue to merge, then merge/rebase your pull request
  with the latest changes to then work on a proper fix.
• Once the issue is fixed, delete the /wait comment and
  follow the usual process to merge the pull request.