JENKINS-47882 Upgrade mongo client to 3.x and jackson to 2.x

[timja]

Note,
I've tried to upgrade dependencies but not APIs in this PR, there's deprecated code and new apis that should be used in a follow up PR.

This PR will make allowing the use of SSL simple (https://issues.jenkins-ci.org/browse/JENKINS-45315)

This may resolve https://issues.jenkins-ci.org/browse/JENKINS-49140 or at least make it much easier to achieve

[timja]

@rsandell can you please review?

[rsandell]

@timja by merging your other PRs this now needs to resolve some merge conflicts :)

[timja]

done @rsandell most trivial resolve ever

[rsandell]

Is there some good/"simple" way to test that a old database stored by the old code/driver can be read back using this code?

[timja]

Not that I'm aware of, but upgrading the driver was able to read old data just fine.
the old driver also worked on new mongo
except for authentication methods, i.e. old driver couldn't handle the new required auth mechanisms

[wfreemanben]

After this change, I'm unable to connect to Mongo v3.4.18 , but rolling back to the previous version (of the plugin) I can again. Is there some sort of migration or re-configuration required to make this work?

[timja]

shouldn't be, i'm using 4.x but the tests are using 3.6
https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/89/files#diff-b49a3adcb5396a868ad161dea2330235R85

are you using authentication?

[wfreemanben]

Tried with and without, with the same results.

[timja]

I'll try take a look in a couple of days, looking at the docs the version is supported:
http://mongodb.github.io/mongo-java-driver/3.8/upgrading/

[timja]

What stacktrace do you get @wfreemanben ?

I tried it out, and had trouble with no authentication, but with this PR I'm able to connect fine to 3.4.18:
#95