fix: add task config to version hash calculation

[ddl-rliu]

Tracking issue

Closes flyteorg/flyte#5364

Why are the changes needed?

Failed to register a workflow if users update the task config – especially in the case of custom tasks

What changes were proposed in this pull request?

hash should be calculated from the task config

How was this patch tested?

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Tangentially related PRs:
flyteorg/flyte#4904
#2356
#2120

Docs link

[ddl-ebrown]

FYI there's a failing test b/c the mocked call isn't expecting the new param

=========================== short test summary info ============================
FAILED tests/flytekit/unit/remote/test_remote.py::test_get_image_names - AssertionError: expected call not found.
Expected: _version_from_hash(b'\x01\x02\x03', <ANY>, <ANY>, 'flyteorg/flytekit:5QQUz7hCXJyIkYOg6eFl0w')
Actual: _version_from_hash(b'\x01\x02\x03', SerializationSettings(image_config=ImageConfig(default_image=Image(name='default', fqn='cr.flyte.org/flyteorg/flytekit', tag='py3.12-latest', digest=None), images=[Image(name='default', fqn='cr.flyte.org/flyteorg/flytekit', tag='py3.12-latest', digest=None)]), project=None, domain=None, version=None, env=None, git_repo='', python_interpreter='/opt/venv/bin/python3', flytekit_virtualenv_root='/opt/venv', fast_serialization_settings=FastSerializationSettings(enabled=True, destination_dir='.', distribution_location='localhost:30084'), source_root=None), {'name': 'union'}, 'flyteorg/flytekit:5QQUz7hCXJyIkYOg6eFl0w', 'None')
====== 1 failed, 926 passed, 62 skipped, 690 warnings in 73.57s (0:01:13) ======

Basically the line at

flytekit/tests/flytekit/unit/remote/test_remote.py

Line 505 in 1ca3d91

version_from_hash_mock.assert_called_once_with(md5_bytes, mock.ANY, mock.ANY, image_spec.image_name())

needs to be updated for the None at the end

[ddl-rliu]

Is it preferred to gate this behavior behind config? If so, it likely doesn't belong in the PlatformConfig section – happy to move it somewhere else.

[ddl-rliu]

Closing in favor of #2428