fix: Add proper startupProbe checking if startup is completed

[sbernauer]

Description

While testing a the new trino-lb feature stackabletech/trino-lb#63, we noticed that the TrinoCluster turns healthy before it is ready to accept queries.
This PR fixes that, especially in combination with stackabletech/trino-lb#68

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

# Author
- [ ] Changes are OpenShift compatible
- [ ] CRD changes approved
- [ ] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Helm chart can be installed and deployed operator works
- [ ] Integration tests passed (for non trivial changes)
- [ ] Changes need to be "offline" compatible

# Reviewer
- [ ] Code contains useful comments
- [ ] Code contains useful logging statements
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added
- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated

[maltesander]

nice LGTM!

[lfrancke]

Can you please add a release note snippet in the form "Previously, . With this release, ."

[sbernauer]

I don't think this needs a mention in the platform release notes, so I'd say the changelog is sufficient.

• Add a startupProbe, which checks via /v1/info that the coordinator/worker have finished starting.
  Also migrate the other probes from tcpSocket to httpGet on /v1/info ([fix: Add proper startupProbe checking if startup is completed #715]).

If we want to change the wording, we need to change it in the changelog, should I raise a PR?