I'm sorry I'm not ready to accept this as a solution. I'm not saying you are not right though. The documentation is not clear on this, or I would say that there are contraindications.

Add tasks to jobs in Declarative Automation Bundles | Databricks on AWS:

"..., because local relative paths may not point to the same content in the Git repository."

I'm not using relative imports to import my shared modules.

"Instead, clone the repository locally and set up your bundle project within this repository, so that the source for tasks are the workspace."

It was my understanding that when job starts it clones the repository locally to the cluster and therefore it should behave correctly: Use Git with Lakeflow Jobs | Databricks on AWS