feat(hpa): Allow setting apiVersion through values file

[stijnbrouwers]

With K8s v1.25 being available, the HPA apiVersion has changed.

apiVersion: autoscaling/v2beta1

is deprecated in favour of

apiVersion: autoscaling/v2

The change still uses the same default value for the apiVersion as before (since not everyone will have migrated to v1.25 yet) but it's now possible to change the value through the values-file

[stijnbrouwers]

FYI, @lewismc

[lewismc]

Excellent @stijnbrouwers thanks.
Same question as I asked @frascu , when I make the new Helm Chart release, should we align the Helm Chart version with the upstream Dockerhub tika version or simply make it latest-full? Any thoughts...? Ideally I would like to automate the Helm Chart releases based on new upstream Docker releases but I don't really have time to implement that right now.

[stijnbrouwers]

@lewismc, personnaly, I like the appVersion in the chart.yaml file to be equal to the tika version that's being used by default. Keeping the chart version in sync is not necessary and maybe even difficult or impossible since there might be multiple chart updates during a single version.

An automatic build based on the upstream would indeed be ideally, I'll try to keep it in mind for a nice future project since I don't have the time for it atm either :-)

Thanks for merging btw!