[flytekit/eager] Move the type engine invocation to the worker itself

[wild-endeavor]

Describe the issue

Eager tasks kick off other Flyte entities when it runs against a Flyte backend. These executions need inputs in the form of Flyte literals of course. The translation of Python native values into these Flyte literals is currently being done by a FlyteRemote instance. This is okay for now but it's not ideal. The reason is that these input values form part of the hash that's used to consistently name downstream executions. We should hash the Flyte literal value to be most accurate, rather than the Python value.

What if we do not do this?

Consistent hashing of execution names is suboptimal and may lead to bugs down the road.

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes