fix: don't loose build num

[msvticket]

prevent build num from resetting

The solution consist of 2 parts:

1. Make sure that all finished pipeline activities are garbage collected from cluster (now some failed ones stay)
2. If there are no pipeline activities in the cluster: check the logs bucket and extract the latest build num from there

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign msvticket
You can assign the PR to them by writing /assign @msvticket in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[msvticket]

/retest

[msvticket]

/retest

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jenkins-x-bot]

@msvticket: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pr	8fd40af	link	/test pr

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.