chore(deps): bump github.com/devfile/devworkspace-operator from 0.42.0 to 0.43.0

[dependabot]

Bumps github.com/devfile/devworkspace-operator from 0.42.0 to 0.43.0.

Changelog

Sourced from github.com/devfile/devworkspace-operator's changelog.

v0.43.0

Bug Fixes & Improvements

• Apply configured imagePullPolicy from DevWorkspaceOperatorConfig to backup CronJob containers instead of hardcoding Always #1654
• Apply configured podSecurityContext from DevWorkspaceOperatorConfig to backup CronJob pod templates #1655
• Fix SSH askpass script responding to non-passphrase prompts (e.g. HTTPS username/password requests), causing "passphrase file is missing" errors during project cloning #1658
• Document controller.devfile.io/allow-import-from annotation for cross-namespace DevWorkspaceTemplate imports #1673

Commits

• 5e84167 [release] Add OLM bundle for v0.43.0 in 0.43.x
• 9655b77 fix: restore empty v0.42.0 release-digest bundle
• dcbd21a [prerelease] Prepare branch for release
• 4802c81 docs: create DWO 0.43.0 changelog
• 7cc5b95 chore(deps): bump google.golang.org/grpc from 1.79.3 to 1.82.1 (#1676)
• 1f86ade chore(deps): bump go version to v1.26.5 (#1671)
• 675d5e6 chore(deps): bump golang.org/x/crypto, x/net, and x/mod to latest (#1670)
• 8481361 chore (deps) : update controller-runtime to v0.24.1 (#1642)
• 5413a98 fix(backup): apply configured podSecurityContext to backup CronJob (#1655)
• 1cd06ee fix(backup): use configured imagePullPolicy for backup CronJob (#1654)
• Additional commits viewable in compare view

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]

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

Details

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

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a eclipse-che member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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 kubernetes-sigs/prow repository.