Move Data Explorer (TM) over from Enterprise Web

[nhaugo]

In order to get the first version of Chronograf Nuevo up and running, we'll need to bring over a front end component to get the test suite up and running so that we can start building around the new toolchain. The first candidate that makes sense for this is the Data Explorer.

Here are the assumptions we can run with for this:

• Continue using the existing visual design
• Ignore all other sections of Enterprise Web - overview, user management, cluster management, etc
• Assume that there is already a backend node/cluster configured (i.e. there is no requirement for configuration screens)

[kfitzpatrick]

Has a dependency on #5.

[wfro]

Assume that there is already a backend node/cluster configured (i.e. there is no requirement for configuration screens)

Is this just a plutonium instance? Are we ready to start porting the data explorer to use the new backend (even if it's just swagger mocks)?

The actual porting should hopefully be straightforward. I do have a few questions, mostly around the data explorer's backend dependencies.

We need two backend things to consider the data explorer functional:

• A server to save "sessions" to. Right now we just need a table with a name and a data field that stores a json blob.
• An endpoint to sign and attach JWT tokens to InfluxDB queries (the client still requests all of the data nodes and picks which one to make each request to).

For this first pass should we:

1. Keep things as simple as possible and use what we currently have (and possibly even mock query data)
2. Start updating the frontend to use new endpoints

[nhaugo]

• There is no need to hook up to an actual data source, mocked data should be plenty to satisfy the goal.
• Sessions can be mocked as well. We should probably review the session object to ensure we are not carrying over unnecessary technical debt.
• Sessions can be temporary so buttons that write data can be left alone and do not need to function.
• The goal is to port over the ui not wire everything up.

[wfro]

Thanks @nhaugo, this should be all set then. Once #1002 and #1036 make it into the enterprise code, hopefully by tomorrow, we can move the entire data explorer (it makes sense to do it there, there is work in progress on those two features so it's more difficult to move the code and then complete them).

[nhaugo]

Sounds good!