Ch 819: editHtml personalize element variation

Allow a variation type to be retired by still available for backwards compatibility.
Add an editHtml personalize variation type.
Created a callback mechanism for edit in context:
* I placed this in the main personalize_elements.js file and I'm conflicted about that.  The structure was there to support multiple callback types per variation type but it's technically the admin layer and not the main layer.  However, I also don't want to add even more javascript files to the page when we only need a little callback.  I welcome new thoughts on this... it would be easy enough to move if there was something else that worked better and felt less cludgy.
Of course it doesn't make sense in visitor_actions (now that I've written it) - it actually makes sense in visitor_actions_ui but I don't want to introduce a dependency on that in personalize.  Is it horrible to have it in visitor_actions so that it can be accessible by those modules in need even if its not really used there?