chore(vector): Update major/minor versions for 26.3.0

[NickLarsenNZ]

Part of #1368.

• Add: 0.52.0
• Remove: 0.49.0

Important

• Uses stackable-base.
• Used as a base for java-base.

Update tasks

• Update boil-config.toml to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
• Update the stackable-devel/boil-config.toml for the applicable toolchain version for the vector builder.
• Update all boil-config.toml files which reference vector.
• Add any patches required for this version (delete patches for removed versions).
• Update other dependencies if applicable (eg: inotify_tools, etc).
• Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR(s) to the list below.
• Update the version in demos. Add the PR(s) to the list below.

Related Pull Requests

Tip

Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

• chore: Bump vector to 0.52.0 for SDP 26.3.0 #1387
• Link to any other operator PRs (getting_started / kuttl)
• Link to demo PR (raise against the main branch)
• Link to the Release Notes PR in the documentation repo (if not a comment below)

Acceptance

Tip

This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been
checked, the issue can be moved into Development: Done.

• Can build image (either locally, or in CI)
• Kuttl smoke tests passes (either locally, or in CI)
• Release notes added to documentation and linked as a PR above
• Release notes written in a comment below
• Applicable release-note label added to this issue

Testing instructions

# Where x.y.z is the new version added in this PR
boil build vector=0.52.0 --strip-architecture --load

kind load docker-image oci.stackable.tech/sdp/vector:0.52.0-stackable0.0.0-dev

# Change directory into one of the operator repositories and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar

Please consider updating this template if these instructions are wrong, or
could be made clearer.

[NickLarsenNZ]

Now that the patch has been applied upstream, we have the option of going back to pulling the binary instead of building from source.

I would propose we keep building from source because:

1. It is slightly easier than reverting, and
2. I'd (eventually) like to slim down the artifact by limiting the features it builds with.