Allow Stapler to accept 'kind' in addition to 'stapler-class'.

Today, Jenkins uses a mix of stapler's data-binding and its own.  The former uses a lot of 'stapler-class[-bag]' annotations, whereas the latter uses 'kind'.  Various jelly elements emit both because they aren't sure which is needed.

This change allows Stapler to accept 'kind' in addition to 'stapler-class', so that a single-consistent term may be used for all contexts.

NOTE: The bias here is towards 'kind' because this keyword choice directly affects the grammar of the yaml-project plugin, and is a more user friendly keyword for the YAML DSL.
This shifts the attribute used by Stapler from 'stapler-class' to '$class'.

Per discussion on https://github.com/stapler/stapler/pull/39, this changes the name of the special Stapler attribute from 'stapler-class' to '$class'.
Just to be on the safe side, honoring 'stapler-class' as well

.. but with a logging, so that we can see who is still using it.
Merge pull request #39

Going with '$class' after talking to Matt & Jesse in the same room.