[BUG] InvalidImageName errors are not reported correctly

[katrogan]

Describe the bug
InvalidImageName errors are not reported in the UI leading to confusion when tasks are stuck pending without logs or other debug information.

Expected behavior
The UI should indicate a task failed because of InvalidImageName

Flyte component

• Overall
• Flyte Setup and Installation scripts
• Flyte Documentation
• Flyte communication (slack/email etc)
• FlytePropeller
• FlyteIDL (Flyte specification language)
• Flytekit (Python SDK)
• FlyteAdmin (Control Plane service)
• FlytePlugins
• DataCatalog
• FlyteStdlib (common libraries)
• FlyteConsole (UI)
• Other

To Reproduce
Steps to reproduce the behavior:

1. ...
2. ...

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
Flyte component

• Sandbox (local or on one machine)
• Cloud hosted
  • AWS
  • GCP
  • Azure
• Baremetal
• Other

Additional context
This is very similar to #244

[kumare3]

@katrogan we do show ImagePullBackoff failures. Is this not enough? Can we please close this bug, if this solves the issue?

[katrogan]

@kumare3 i observed this while on-call after your ImagePullBackoff change was merged

[kumare3]

An example would be great

[katrogan]

  Warning  Failed         7m29s (x5053 over 18h)  kubelet, ip-10-44-163-228.ec2.internal  Error: InvalidImageName
  Warning  InspectFailed  2m33s (x5077 over 18h)  kubelet, ip-10-44-163-228.ec2.internal  Failed to apply default image tag "12345.dkr.ecr.us-east-1.amazonaws.com/repo:flyte.{{ salt['environ.get']('IMAGE_VERSION') }}": couldn't parse image reference "12345.dkr.ecr.us-east-1.amazonaws.com/repo:flyte.{{ salt['environ.get']('IMAGE_VERSION') }}": invalid reference format```