chore: attest provenance for images

[prakrit55]

• [x] added provenance mode to max for images

Fixes #3310

Checks

• [ ] My PR fulfills the Definition of Done of the corresponding issue and not more (or parts if the issue is separated into multiple PRs)
• [ ] I used descriptive commit messages to help reviewers understand my thought process
• [ ] I signed off all my commits according to the Developer Certificate of Origin (DCO)( see Contribution Guide)
• [ ] My PR title is formatted according to the semantic PR conventions described in the Contribution Guide
• [ ] My content follows the style guidelines of this project (YAMLLint, markdown-lint)
• [ ] I regenerated the auto-generated docs for Helm and the CRD documentation (if applicable)
• [ ] I have performed a self-review of my content including grammar and typo errors and also checked the rendered page from the Netlify deploy preview
• [ ] My changes result in all-green PR checks (first-time contributors need to ask a maintainer to approve their test runs)

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.31%. Comparing base (0f38104) to head (23c1841).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #3421 +/- ## ======================================= Coverage 85.31% 85.31% ======================================= Files 167 167 Lines 7415 7415 ======================================= Hits 6326 6326 Misses 800 800 Partials 289 289 ``` | [Flag](https://app.codecov.io/gh/keptn/lifecycle-toolkit/pull/3421/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn) | Coverage Δ | | |---|---|---| | [certificate-operator](https://app.codecov.io/gh/keptn/lifecycle-toolkit/pull/3421/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn) | `69.23% <ø> (ø)` | | | [component-tests](https://app.codecov.io/gh/keptn/lifecycle-toolkit/pull/3421/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn) | `58.04% <ø> (ø)` | | | [lifecycle-operator](https://app.codecov.io/gh/keptn/lifecycle-toolkit/pull/3421/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn) | `83.42% <ø> (ø)` | | | [metrics-operator](https://app.codecov.io/gh/keptn/lifecycle-toolkit/pull/3421/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn) | `88.32% <ø> (ø)` | | | [scheduler](https://app.codecov.io/gh/keptn/lifecycle-toolkit/pull/3421/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn) | `34.74% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=keptn#carryforward-flags-in-the-pull-request-comment) to find out more.

[mowies]

@prakrit55 please do a release in your fork with your own container registry to prove that this works :) The release pipeline can be pretty fragile so it would be good to thoroughly test this before it's merged

[prakrit55]

@prakrit55 please do a release in your fork with your own container registry to prove that this works :) The release pipeline can be pretty fragile so it would be good to thoroughly test this before it's merged

the job build-release in release please workflow is skipping, do I need to check anything else

[odubajDT]

@prakrit55 please do a release in your fork with your own container registry to prove that this works :) The release pipeline can be pretty fragile so it would be good to thoroughly test this before it's merged

the job build-release in release please workflow is skipping, do I need to check anything else

Hi @prakrit55 you need to start the release workflow manually either by starting it from the Github actions or by merging the release-please PR which was automatically created o your fork

[prakrit55]

hey @odubajDT, not sure, if its the right step but it was skipping from the first, I modified and ran the workflow