Increase case search timeout

[BryceStevenWilley]

I was told that Tyler's servers on production were fast enough, but I got reports of several timeouts of case searches on production today, even though:

• users can only search for case numbers, not for people; case numbers has always been fast for me
• it was timing out after 60 seconds, even though there should be a timeout for 90 seconds? Hard to tell who originally throws the timeout, and how to stop it.

To mitigate;

• need more details of where (which courts) people are searching in, and how (just name or case, no more details), so we can try to reproduce more accurately
• increase the timeout to 2 minutes in the code
• see if there's somewhere else that's throwing a timeout early, based on the stack trace

[BryceStevenWilley]

We able to consistently reproduce this issue, which let me experiment with a bunch of different and outdated ways of fixing this[^1]. The ones that worked were:

• in the question of https://stackoverflow.com/q/38824218/11416267, and using jakarta.* as well as javax.*
• https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-HowtoconfiguretheHTTPConduitfortheSOAPClient?

The latter option IMO is cleaner, and doesn't require any arcane config strings, only arcane classes 😜

Will make a PR with this soon

[^1]: For posterity, these solutions do not work: https://stackoverflow.com/a/7512962/11416267, https://stackoverflow.com/a/14642929/11416267