Sorting keys wherever we render inputs/outputs

[schottra]

flyteorg/flyte#98

Object.entries and Object.keys don't guarantee an ordering. This is normally not a problem, except we directly render the result of calling these functions on an input/output object to the screen.
Since the API response also does not guarantee ordering, this can mean a re-ordering in the rendered content when we are polling for execution status and/or changing launch plan versions.
Consistency of display is preferred to optimal ordering of values, so for now we will sort the values lexicographically.

• Added helper functions for calling Object.entries and Object.keys and subsequently sorting the resulting arrays
• Updated the three places we use those built-ins to generate output to call the sorted versions instead.
• Wrote tests for the components in question to ensure that sorting is correct in the generated DOM elements.