Update Redpanda chart dependencies

[andrewstucki]

This builds on #654 and updates the redpanda chart to use the versions of console/connectors found there as well as introducing the updated gotohelm. After this we should be able to get away with referencing newer versions of pkg that no longer contain gotohelm in projects that depend on the chart.

[RafalKorepta]

Dependencies on commits from github.com/redpanda-data/redpanda-operator modules MUST be present in main, release/*, or be a git tag.
--
  |  
  | github.com/redpanda-data/redpanda-operator/gen: "github.com/redpanda-data/redpanda-operator/charts/connectors@v0.0.0-20250407180246-dc814fb6b3b8"
  |  
  | dc814fb6b3b8 could not be resolved via git merge-base --is-ancestor dc814fb6b3b8 <acceptable-branches>

Linter is failing

[andrewstucki]

@RafalKorepta yeah -- I'm trying to figure that out, the SHAs updated are the tip of release/v2.4.x -- so not entirely sure what's up (or maybe I'm just not understanding our lint test message - i.e. does it need to be a tag?)

[andrewstucki]

looks like our RELEASE_BRANCH file (not sure what that's used for apart from this test) still had v2.3.x in it.

[chrisseto]

looks like our RELEASE_BRANCH file (not sure what that's used for apart from this test) still had v2.3.x in it.

Didn't you add that file? 😛

I want to say it's used to convince either GHA or BK to fetch additional refs required for that test?

[andrewstucki]

I don't believe I did, but I might have 😅

[RafalKorepta]

I don't believe I did, but I might have

I did that. https://github.com/redpanda-data/redpanda-operator/commits/release/v2.3.x/RELEASE_BRANCH

I'm not sure why. Maybe some kind of file generated by backport-cli. It should not be used by any test, GHA nor BK as far as I know.