Hyper.Graphics should be an alias for a Blaze.Html type

[amigalemming]

For Hyper.Display instances for container types it would be nicer to work on Blaze.Html. I could then call Hyper.display on the container elements and arrange the obtained HTML objects on the HTML level. Blaze.Html would be better for composability than Text.

[HeinrichApfelmus]

In the medium term, I would like to make the Hyper.Graphics type more compositional, but I am reluctant to just use HTML for that. It would be a nice short-term solution, but quickly evolve into a de-facto standard that we cannot get rid of. I would like to keep Hyper.Graphics abstract.