TCK must check serializers better

TCK as of Jakarta EE 8 does not detect the following violation of the JSON-B specification 1.1:

- Johnzon does not implement JsonbConfig#with(De)Serializers, but instead throws an exception, while the JSON-B specification does not explicitly say that support of that methods is *optional*. Users of the spec will interpret the chapter as "all JSON-B implementations will support that", and run into problems when using Johnzon. Either the TCK has to be more strict, or the spec has to be more clear.
- Yasson runs deserializers *alyways* even for classes *not* being matched by the generic type of the deserializer.

See also the discussion between @romain-grecourt and me in #184

Closing #184 hereby, as it ended up in the decision that most likely the TCK is not strict enough.

Start with the Jakarta EE 8 TCK tests for JsonbConfig#with(De)Serializers and the serializer/deserializer coverage described here; issue #184 records the prior discussion. Done means the TCK detects the reported Johnzon and Yasson behaviors, or the expected scope is resolved against the JSON-B specification.

Written by the indexing model from the issue text.