Features server

Change some logging messages in the JsonHelper-class from debug to trace
the SchemaAttributes-methods are now public. This allows dynamic configuration changes during runtime
The binary type is now supported
Support ms-azure patch-notation for replace and add-operations
Support for ms-azure patch-requests with filter-expressions. This feature must be explicitly activated.

Features client

Make getResource-method in RequestBuilder public. This can be used to easily find the corresponding request-objects of bulk-response-objects
Add several convenience methods to the BulkBuilder class
Allow parallel handling of BulkRequests. The client has in inbuilt feature to split a BulkRequest into tiny pieces by honoring the maxOperations-value of the ServiceProvider. These tiny pieces can now be sent multithreaded.
The expected response-headers of the client can be changed. Normally the client expects to receive the response-header Content-Type: application/scim+json but some providers do not send this header. To prevent the response from being rejected simply override the expectedHeaders in the configuration.
Add a convenience method to add a list of values in PatchBuilder
Updated bouncycastle from bcprov-jdk15on to bcprov-jdk18on and bcpkix-jdk15on to bcpkix-jdk18on

Fix missing operations in bulk-response. If the precondition of a bulk-request failed the following response-objects were not added to the response
Changed log-message in ResourceTypeFactory. Due to a bug in the equals-method of jackson-JsonNode the comparison of the objects fails and the log-message is erroneously displayed. The message was changed to debug in hope that the comparison bug will be fixed in a later version.
A Bug was fixed that caused the response to fail with HTTP 500 if the attributes or excludedAttributes parameter was used. The parameters could cause a required-attribute to be missing in the response. Required-attributes will no longer be handled as required in the response if the attributes or excludedAttributes parameter was used.
Fixed a serious bug in bulk-requests that were introduced with version 1.15.0. If some operations did not have a bulkId it might have happened that some operations were executed twice or more often and other operations were never be processed. This was fixed by implicitly adding bulkIds to all operations that had no assigned by the client.

Fixed a bug that was caused if a returned bulk-response operation did not have an id. This might happen on singleton-endpoints.