Decide if Canvas Workbench is the final name

Overview

In #3573867: Start prototyping Canvas Workbench, we added a new JS package within the Canvas monorepo: @drupal-canvas/workbench. That issue summary says that "workbench" is a working (meaning, not final) name. There's a lot to like about the name with respect to its metaphor: in many ways it has the same relationship to the Canvas module as an artist's workbench has to an artist's canvas. However, #3573867-10: Start prototyping Canvas Workbench points out that even though it's a JS package and not a Drupal module, when we refer to it as "Canvas Workbench" people might assume it has something to do with integrating Canvas with the popular Workbench Drupal module, which it does not.

Proposed resolution

Decide if the context is sufficiently separate from the Workbench module, that it's okay to use the same name for an entirely different concept.

If we decide that the context isn't sufficiently separate, then pick a new name. Perhaps something like ide or localdev or ...?

User interface changes