Test case: class changes propagate to translations when published
Make publishing default locale node faster

When you publish a node in the default locale it calls forceChange to make
every field behave as if it has changed. The problem in Translatable is then
it would think that you actually changed the class of the default locale node
and it would force a change on every translation. This was unnecessary when you
have not actually changed the class name. If you have a great deal of
translations this was causing a significant lag when you publish anything in
the default locale.
Merge pull request #132 from jthomerson/pulls/only_write_translations_when_class_actually_changed

Only write translations when class actually changed