I'm attempting to narrow down a bug in Flyte v1. When we do nothing but add one our private internal packages to a uv.lock that we pass into a workflow that makes use of map_task we get the following error (I'll post the full stacktrace in the thread):

ModuleNotFoundError: No module named 'site-packages.flytekit'

This causes a change down which seems to affect the container args (I'm not sure what these are), but we get this because if I change the dependencies on the image but not the tasks in the workflow I get an error asking me to re-register the task:

/template/Target/Container/args/23:
	- flytekit.core.python_auto_container.default_task_resolver 
	+ site-packages.flytekit.core.python_auto_container.default_task_resolver

... I believe the error "No module named 'site-packages.flytekit'" occurs because load_object_from_module() gets passed *site-packages.*flytekit.core.python_auto_container.default_task_resolver and not flytekit.core.python_auto_container.default_task_resolver but I don't know what leads to this import path being passed in. I'll post a minimal working example package that causes the break once I've factored one out, but does anyone know what's happening here?