Fix passing null to Mockito in meta-property tests

A "simple refactoring" lead to a null reference being passed to Mockito instead of a mock. This caused most tests to fail.
Support write-only meta-properties

According to the discussion in #3: "Since Java Beans v1.0 allows write-only properties, I suspect we have to allow for them, but not beyond the basic possibility of an exception. Adding an isWriteOnly() method seems like overkill." (jodastephen) 'AbstractMetaProperty' now supports write-only properties according to 'MetaProperty.get(Object)'.

Additionally the order of the Boolean constructor arguments was changed to reflect the order of the methods in 'MetaProperty'.
Move reusable parts of 'FieldMetaPropertyTest' into own class

Most of the code from the test class is chaining factory methods and only one method actually creates instances. Only the last one is specific to this test; the chaining methods can be reused for every test class which can create a 'MetaProperty' based on the name of a field. Hence an additional abstract class was introduced which only leaves the method which creates an instance for a field name abstract.
Partly implement 'MetaProperty' which uses reflection on methods to access values

The created 'MethodMetaProperty' does not yet access annotations. Besides that class this commit contains the tests (which hence fail, for annotations).
Reorder exceptions in 'FieldMetaProperty'

The exceptions are now caught in a more logical order.