Spike: JetBrains Toolbox Architecture open questions

While exploring the new Toolbox architecture, several questions and friction points have surfaced. We should gain clarity on the below:

[ ] JetBrains should fix the token link used to grab the dashboard token as this is showing in the URL twice
[ ] In the main environment list there is an empty view container that JetBrains should cleanup (or possibly we can fix this on our end but we need their input)
[ ] Nice-to-have We should consider adding telemetry so that we can see what IDEs users are using as well as DAU. Right now, all IDE tracking is lumped into one JetBrains bucket (might not make sense to split them up since there is little technical difference). @stirby to poke into the priority of this item.
[ ] It would be nice to understand how Toolbox performs compared to the existing Gateway. JetBrains has not released any performance benchmarking. We should see if a plugin is available within JetBrains to do some benchmarking of our own.

coder / jetbrains-coder