Flux e2e tests: let to transformation complete even on error.

In `dynamic_query.flux` we have (wrapping up the script):

```
csv.from(...) |> to(bucket: BBB)
from(bucket: BBB) |> ... |> tableFind(fn: (key) => key._measurement == "CPU")
```

`tableFind` triggers an error if it doesn't find a table that satisfies `fn`. The problem is that if `from` and `to` run in parallel, then `tableFind` will error and block `to` from persisting values to InfluxDB.

The solution is to clearly split the `to` and `from` "phases" in e2e tests.

Start with the dynamic_query.flux e2e script and trace how its to and from pipelines are executed. Separate the to and from phases so tableFind cannot prevent values from being persisted, then run the relevant Flux e2e test and confirm the data is available for the lookup.

Written by the indexing model from the issue text.