chore: Cherry pick for 1.4

[binbin-li]

Description

What this PR does / why we need it:

Cherry-pick from dev to release-1.4

We may need to create a merge commit instead of squash commit to keep the commit history.

Ran aks test in my forked repo:

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• Does the affected code have corresponding tests?
• Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
• Does this introduce breaking changes that would require an announcement or bumping the major version?
• Do all new files have appropriate license header?

Post Merge Requirements

• MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
pkg/verifier/notation/truststore.go	93.02% <100.00%> (+0.16%)	⬆️

[susanshi]

LGTM. thanks binbin

[susanshi]

@binbin-li , whats the best way to run the aks test on the latest changes for the release branch?

[binbin-li]

@binbin-li , whats the best way to run the aks test on the latest changes for the release branch?

since it's a PR from fork, we cannot run the aks test. I'll run it in my forked repo and post result here. Another workaround is to create a cherry-pick branch under ratify repo and merge from it but it's not applied to all contributors except maintainers.