[BUG] When Memory/CPU/Storage/GPU limits are over the platform prescribed limits, Flyteadmin error is not descriptive

[kumare3]

Describe the bug
FlyteAdmin Error should clearly state what the problem was and potential remediation. For example, if the user requests for cpu limit that is over the platform prescribed limits then the error should state so and also provide actual limit currently set in the platform.

If parsing of the CPU limit fails then the error should be more descriptive

E.g error recived

	details : "Type CPU for [resource_type:TASK project:"flytesnacks" domain:"development" name:"demo.house_price_predictor.generate_and_split_data" version:"6755f982790bcf96a00229ac7a9981235c4554a2" ] cannot set default > platform limit"

Reason: "200Mi" was not being parsed correctly

Expected behavior
Better error message when request is more than the limit
e.g

Requested CPU [x] is greater than current maximum set in the platform configuration [y]. Please contact Flyte Admins to change these limits or consult the configuration

If parsing fails

Parsing of CPU request failed - reason 'x'. Please follow K8s conventions for resources https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

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

[kumare3]

@katrogan this sounds like a low hanging fruit