feat(ui): Argo Events API and UI. Fixes #888

[alexec]

Checklist:

• My organization is added to USERS.md.

Features

• New API endpoints for Argo Events
• New event-flow page
• Create, edit, view, log event sources and sensors in the UI
• Embeddable widgets
• New workflow log viewer
• Configurable "Get help" button
• Refactored code to use more robust React functional components
• Seemless reconnection on network errors
• Many small tweaks
• Lots of bugs fixed

Fixes #888

[alexec]

@jessesuen @sarabala1979 @simster7 I'm pondering what to do with this PR now. It does contain two major items: the Argo Events UI and the GUI workflow editor. However, we now have feedback that a workflow editor is not very useful to users, one person found it confusing.

One option - only have Argo Events :

• Remove the workflow editor from this PR and only have the Argo Events code. Maybe be do a later PR for that code.

Pros will reduce complexity and bugs
Con: loses lots of code refactored to use useEffect which is 10x easy to debug.

Thoughts?

[simster7]

@alexec I am a fan of a lot of the code refactors in this PR, including useEffect. Is it feasible to revert just the Workflow editor and keep the rest in? I'd be happy to discuss my ideas more in depth during stand up, I gathered some feedback on the UI and was planning on sharing anyway.

[alexec]

@simster7 lets discus at stand-up. I think v3.0 is really pack with stuff and we're going to need to really focus and push to get it out in the time frame MK's requested.

[jessesuen]

Note, that if you use {sensor.metadata.name} instead of {name}, then you don't need to introduce a name field in UpdateSensorRequest.

i.e.

put: "api/v1/sensors/{namespace}/{sensor.metadata.name}"

[alexec]

nice - we should leverage this all over