Read timeout to overpass-api after 120000 ms

Hello,

I love to create challenges with Overpass API, but recently I 'saw' that the default timeout was lowered from 180s to 120s 😭

So I read the source code and I saw that if my overpass query start with [out:json] or [timeout:_TIME_] then Maproulette should take in account my 'custom timeout'. But sadly something is not working properly and my custom timeout is not used.

Here is a way to reproduce the issue:

1. Create a challenge with the following overpass query:

[timeout:180];
node[amenity=drinking_water];
out;
// DO NOT USE THIS QUERY FOR REGULAR CHALLENGE
// Because It queries all the drinking water node worldwide!!!

or the same query but starting with [out:json][timeout:180]

2. Run the challenge
3. Wait 120s to get the following error message Read timeout to overpass-api.de/xxx.xxx.xxx.xxx:80 after 120000 ms
4. BUG! The query should have stoped at the correct 180s timeout and not an arbitrary 120s.

Part of the code to handle this timeout is in this file: ChallengeProvider.scala

Thanks all contributors for the good work done on Maproulette ❤️

Start in app/org/maproulette/provider/ChallengeProvider.scala and trace how the Overpass query's timeout is parsed and applied. Reproduce the issue with the documented [timeout:180] challenge query and observe the 120-second failure. Done means the custom 180-second timeout is honored instead of the default 120 seconds.