Static content optimization causes different hydration mismatch behavior for `class`/`style` order

[nolanlawson]

If you have a template like this:

<template>
  <div class={classes} style={style}></div>
</template>

And if the content is the same on the server and another on the client, except that the ordering is different:

// server
classes = 'a b'
style='color: red; background: blue;'

// client
classes = 'b a'
style='background: blue; color: red'

...then you get a hydration mismatch in the non-static-optimized case, but no mismatch in the static-optimized case.

This is kind of an edge-case-of-an-edge-case, but opening the issue to track this.