Class descriptors for other DnD tags + style block alignment rework

[Ntbrown]

The amount of bloat generated by this is embarrasing - frankly.

Every last piece of this is encapsulatable by utility classes and you could either 1) supply your own utility class to avoid this bloat we're it possible - but in stereotypical HubSpot fashion you can't or 2) allow thematic definitions that `hook` into the style tabs rendering output to add utility classes to the flex / block definition instead of generating an entire stylesheet worth the repetition in the head of the page needlessly.

The likelihood whatever css framework (🤢) you're using or your theme css doesn't already have these is very slim and even if you didn't definining them and preventing the option for this is still 1000x betters than the generated mess.

Another great release. Here's the track record so far I believe.

1) "Hey guys we have themes now" -> Suck with absolutely 0 interoperability and still requires module definitions and splits for anything more complex than trivialities (so virtually everything of real value).

1a) "Hey guys you can use your own grid now" -> But, wait you still have to use our own interpretation of what this is as our editing interace inherently imposes a 12-column grid upon you and you'll definitely need to include that and let's also completely ignore the ridiculous amount of page bloat that comes with that that could have been solved if we had actually provided the feature we've claimed.
2) "Hey guys we have responsive options now" -> half baked release ~ 1 year ago that still **bleep** and was never finished as you "work through the implications"
3) "Hey guys we have style options now"  -> another half baked release that much like themes yet again fails to provide anything of value to developers and in fact actually causes problems per the post. And, of course, in stereotypical HubSpot fashion the excuse here will be "our focus is marketers and ease of use" because apparently you've missed the point that you can in fact do both if you stopped doing half baked releases and provided anything of value without having to continously patch your old shoddy work. 
3a) Your "style options" on this absolutely kill performance because yet again half baked release without dev focus and guess what! We can't fix this either because we have no interoperability. Good job guys! Another great HubSpot feature - something something CDN, WebP, whatever marketing talk points that makes you sound good to the uninformed!
4) "Hey guys you can add gradients now" -> looks good to anyone naive enough to think these choppy definitions of gradients suffice and I'm not going to waste my time getting into color stops, smoothing, and color spaces in general and why this **bleep**.