Offer "stable" and "latest (unstable)" tool versions

[ebugden]

Similar to how Trace Compass offers both:

• Core features (stable and well tested)
• Incubator features (less tested, more features)

Trace viewer users could chose between two modes:

• Stable (default): Offers a subset of features that are well-tested and functional. Provides a consistent and predictable experience free from significant bugs or missing pieces. Used by: The average user.
• Latest (unstable): Offers everything implemented on the server (all available data providers) and all partial client features without guarantees. Can include major bugs and missing pieces. Used by: Developers working, testing or demonstrating new features, Tolerant users who don't mind having an inconsistent experience in exchange for more features.

Motivation: To be able to offer a polished experience to so we can start attracting active users (for real-world feedback and information-based design iteration), while also keeping it easy for developers to work on and demonstrate additional features.

[arfio]

I think this is really needed in order to have a stable version which we can show without some end-users having too much trouble running particular analyses that are not yet ready. Also It could improve some features that needs polishing before releasing them and just fix bugs when users file them.

[ebugden]

In the short term, maybe the priority should be to make the default version stable by filtering misbehaving views on the client side. Filtering views is not that much code (ex. Filtering all DATA_TREE views: PR #391) and developers who want to view the unstable version could easily comment the those filtering lines. Since they're missing pieces, I proposed filtering all XY charts for now #472.