Connect: release 0.7.2 is not backward comp with Connect < 2024.05

[pat-s]

As it has a hard requirement on using Connect 2024.05 due to 7789cb2.

Environments using a custom image which is not yet using 2024.05 will fail to upgrade. Yes, one can set TensorFlow.Enabled: false false but an automatic upgrade will fail.
I'd argue that this shouldn't happen for a patch release of the chart.

I am aware that the chart works with the default Connect image of the respective chart version, though in practice I think that a lot of environments use a custom image to have more control about the upgrade process and all of these will fail if they upgrade to this patch release of the chart.

I see two solutions:

• don't enforce TensorFlow.Enabled: true
• release a major version bump (to avoid an auto-update of the chart by common automation tools)

[dbkegley]

Sorry about that. We missed this when considering the upgrade paths. We added Tensorflow to the default container but missed the fact that some users would upgrade the chart without bumping the connect version at the same time, or were not using the default image.

This helm chart assumes that the default configurations will be compatible with the image that posit maintains.