…proj#1382

The `<ObjectEditor>` component used by all the edit pages encapsulates
the logic for serializing/deserializing the object being edited, but
it's extremely inefficient. For example, if you're editing a
`WorkflowTemplate`, every single keystroke will cause `parse()` to be
called twice and `stringify()` to be called 4 times. For large
documents, this serializatino/deserialization overhead adds up quickly.

Additionally, the "Submit" button is sometimes incorrectly grayed out,
e.g. after clicking the "Update" button. This is happening because
`useEditableObject()` is using reference comparisons on the object being
edited, since it doesn't have access to the serialized string version
encapsulated by `<ObjectEditor>`.

This decouples `<ObjectEditor>` from serialization/deseralization and
lifts the state involved up to the `useEditableObject()` hook, as
discussed in
argoproj#13593 (comment).
Doing so eliminates unnecessary serialization/deseralization: now, if
you're editing a `WorkflowTemplate`, each keystroke will only call
`parse()` once and won't call `stringify()` at all. This also fixes
issues with the Submit button not reflecting the current page state,
since `useEditableObject()` now uses string comparisons instead of ref
comparisons.

Signed-off-by: Mason Malone <[email protected]>

Signed-off-by: Mason Malone <[email protected]>