[flytekit/eager] Correctly pipe through serialization settings

[wild-endeavor]

Describe the issue

When a local task is being run through eager, the FlyteRemote instance will register it if it can't find the task, but the serialization settings that are used are not the same as the ones stored in the eager task's transport. This will probably lead to subtle bugs. We should amend remote's registration to handle things correctly.

What if we do not do this?

Subtle bugs will come up as eager tries to register new tasks.

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

• Yes

Have you read the Code of Conduct?

• Yes