Modify the user interaction for Monarch users and include a preview for tactile graphic within the extension

[VenissaCarolQuadros]

Currently (as of #391) Monarch users have 2 additional context menu options to either

1. send the rendering directly to the Monarch or
2. send it to the TAT, make any necessary edits and then send it to the Monarch through the TAT.

This flow is not ideal for sighted users who would like to preview the responses before it is sent to the Monarch but have difficulty using the TAT to do so and BLV users who would like to view the renderings besides the ones sent to the Monarch (such as text or audio).

An alternate flow for this could be to make the tactile renderings appear along with the list of renderings on the extension pop up which would provide a preview of the complete tactile rendering (like the debug view/ something similar TBD) and two buttons to either send it the Monarch or the TAT.

[jeffbl]

I think this captures the key issues. Comments:

• We need to come up with a better name for the TAT, since it will need to be exposed in UI.
• For discussion: I'm not sure we should put up the debug visualization in UI going to end-users, since it is an extra thing to move through, that was really designed only for debugging. So I'd imagine having the debug interface separate from the "send-to" options? So that the visualization can be turned off for production? Or is this valuable enough to expose for verifying the experiences even before they go to the TAT/Monarch?
• If the user has a Monarch attached, we might have to exert more control over the ordering of the experiences, so that Monarch-relevant ones come first, since they are more likely to be selected?
• I think some users may be only using Monarch, and will want a "direct to Monarch" option as currently implemented. But agree that only having this doesn't play well with the existing "list of renderings" UI.