Dependency on version ranges can cause problems downstream

As bson4jackson depends on a version range of jackson-core etc., this can cause problems downstream where the version of jackson being used changes unexpectedly if a new release is created and the version hasn't been fixed by a user of this library.

Could we change the dependency to point to the latest point release of jackson?