"Beta" flag for unstable/confusing features

We know of some features which are half-baked, but nevertheless sometimes useful (such as the minimap) and also we have some things that are confusing (such as the morph menus), but require larger amounts of thought and work to get right.

I propose the implementation of a "beta" or "advancedUser" flag, that will allow usage of these things and, when not set, will hide the corresponding UI elements as well. This way, we can make the UI easier to get into for newer users (as lively.next can be "a bit much" in the beginning in any way).

This flag should be stored in the browsers local storage or in the localconfig and it might be handy to toggle this via the dashboard, similar to the fastload/slowload toggle.

Start by examining the existing minimap and morph-menu UI, then compare the fastload/slowload toggle on the dashboard. Determine whether the setting belongs in browser local storage or localconfig, and define how the beta or advanced-user flag controls visibility of the affected UI elements.

Written by the indexing model from the issue text.