SSP-2184 Remove person.strengths from api IT test data (PG only)
NOJIRA Fix integration test data/ordering dependencies

Each of the integration tests listed in this commit were failing either
because of assumptions about the underlying data set which were upset
by recent additions to the default data set or because unexpected test
execution ordering would break assumptions about API response content.

Also adds a utility for more asserting on API response content on a
JSON field-by-field basis. This required a bump in the JUnit version
to address problems with Hamcrest dependency resolution ordering which,
without the upgrade prevented the new field-by-field assertions from
rendering meaningful failure messages (would get a no-such-method
exception instead).

Conflicts:
	src/test/api/org/jasig/ssp/reference/ConfigIT.java
NOJIRA Fix Hamcrest dependencies

Representative test errors that this fixes:

Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.943 sec <<< FAILURE! - in org.jasig.ssp.reference.ServiceReasonIT
testServiceReasonReferenceAllBody(org.jasig.ssp.reference.ServiceReasonIT)  Time elapsed: 0 sec  <<< ERROR!
java.lang.NoSuchMethodError: org.hamcrest.CoreMatchers.anyOf([Lorg/hamcrest/Matcher;)Lorg/hamcrest/Matcher;
	at org.jasig.ssp.reference.ServiceReasonIT.testServiceReasonReferenceAllBody(ServiceReasonIT.java:267)

testCategoryReferenceSupportedMethodsPositiveChallenge(org.jasig.ssp.reference.CategoryIT)  Time elapsed: 0.439 sec  <<< ERROR!
java.lang.NoSuchMethodError: org.hamcrest.CoreMatchers.anyOf([Lorg/hamcrest/Matcher;)Lorg/hamcrest/Matcher;
	at org.jasig.ssp.reference.CategoryIT.testCategoryReferenceSupportedMethodsPositiveChallenge(CategoryIT.java:303)
NOJIRA Fix api test response length expectations

Reflects additions to the default config and message_template
data sets.