Preload geocoder database, to minimize timeouts

[zachmargolis]

We see a few occasional geocoder timeouts in prod while reading from disk, my hypothesis was that the Geocoder gem lazily loads its datasource.

• Example NewRelic error

In a fresh Rails console in INT, I believe I confirmed this. The first lookup is ~0.1 seconds, and subsequent lookups are at least 200x faster, no matter the order or values, so I am pretty sure the first one forces a lookup

> timing = %w[0.0.0.0 1.2.3.4 8.8.8.8 192.168.1.1].map { |ip| Benchmark.realtime { Geocoder.search(ip) } }
=> [0.08297044999926584, 0.00040709099994273856, 0.0003728679985215422, 0.00019449899991741404]
timing[1..].map { |x| timing.first / x }
=> [203.81302954606332, 222.51963249260257, 426.58548390735075]

The first commit (c4e57b5) was just a personal preference of trying to have "positive" conditions first, which I think reads better.

The "meat" of this PR is 6d2a310

[zachmargolis]

this line is the meaningful change in here (6d2a310)