Cache material data constructors. Fixes BUKKIT-2980

Reobtaining a constructor is not a trivial operation, this change makes the Material enum store the respective constructors for each MaterialData.

Additionally 'fixed' the material tests to use proper generics.
Make RECORD_12 a record. Fixes BUKKIT-3023

Record 12 was missed when added to the Material enum.
Add API for creating explosions without damaging blocks. Fixes BUKKIT-3061
Add data values for entity change block event. Adds BUKKIT-3077, BUKKIT-3076
[BREAKING] Update BlockFace directions. Fixes BUKKIT-1567, BUKKIT-3069

If you use BlockFace in any way, to compensate the directionals being incorrect, you can still have backwards compatibility if you add in the handling in your plugin:
boolean legacyBlockFace = BlockFace.NORTH().getModX() == -1; (and then handle it accordingly)

If you didn't special case your directions to fix what's being fixed here... Hurray! Your plugin should now work.
Add API for controlling mob despawn away from players. Adds BUKKIT-2986
[BREAKING] EntityChangeBlockEvent can be non-living. Adds BUKKIT-3078

Non-living entities can change blocks, specifically falling blocks. This change is a small source break, but mainly a byte-code break (requires plugins to recompile).
Add getShutdownMessage() and stop command arguments. Adds BUKKIT-3031
Deprecate the scheduleAsync methods.

The name is misleading, as it can be misconstrued to mean "a sync"
instead of properly understanding it as "an async"
Add API to get and set collar colors of wolves
Provide a faster way to get a location. Adds BUKKIT-3120

Currently when a plugin wants to get the location of something it calls
getLocation() which returns a new Location object. In some scenarios this
can cause enough object creation/destruction churn to be a significant
overhead. For this cases we add a method that updates a provided Location
object so there is no object creation done. This allows well written code
to work on several locations with only a single Location object getting
created.

Providing a more efficient way to set a location was also looked at but
the current solution is the fastest we can provide. You are not required
to create a new Location object every time you want to set something's
location so, with proper design, you can set locations with only a single
Location object being created.
Add FurnaceExtractEvent. Addresses BUKKIT-2114

Added a "BlockExpEvent" to hold experience and the handlers for the events
An executor set to null will now use the plugin. Fixes BUKKIT-3127
Add isSolid() to Material. Adds BUKKIT-3131

A 'solid' material indicates that it is a block and cannot be passed
through.
Bump JUnit version
Add EntityEquipment API. Adds BUKKIT-3103
Add Material methods. Adds BUKKIT-3161, BUKKIT-3162, BUKKIT-3163,
BUKKIT-3164

This adds an isFlammable method, to indicate if a block can catch fire.

This adds an isTransparent method, to check if light can pass through.

This adds an isOccluding method, to check if it fully blocks vision.

This adds an isBurnable method, to indicate if a block can burn away.
Add ItemMeta factory and interfaces. This adds BUKKIT-15

Included with ItemMeta is a new serializable class Color.

PotionEffects are now serializable.
Clarify functionality in Inventory. Fixes BUKKIT-3097

Mainly javadoc changes to be specific in functionality and outcomes. This is
mixed with specifying that null Material should throw IllegalArgumentException
instead of the previous undefined NullPointerException.

Included is a clarification on how contains(ItemStack, int) works, and a new
method containsAtLeast(ItemStack, int) for counting the number of a specific
item.
Deprecate methods in JavaPluginLoader and PluginClassLoader

These methods are unnecessarily exposed. They are specific to a type of
implementation for the class loaders, and should have no external use.
Because these methods are exposed, it limits the versatility to change
how the internal class loading system works, including an inherent class
loader leak for some situations.

They are now replaced with internal, package-private methods. The public
facing methods will print a stack trace the first time one is activated.

Extending the classes also produces a stack trace, to indicate that
extension is not actively supported.