Fix OTX and Whois data adapter issues

[bernd]

This adds a separate OTX data adaper and uses that one for the OTX API lookup tables to fix several issues and actually makes the OTX features work.

It also fixes the Whois data adapter by adding a client with timeouts.

Notes: This needs to be cherry-picked into 2.4 once merged

---

ATTENTION: Run the following MongoDB shell script via mongo <filename>.js to cleanup the existing lookup table/cache/adapter entries. This is only needed if you are running with a previous 2.4-alpha/beta.

var db = connect("localhost:27017/graylog");

db.cluster_config.remove({type: "org.graylog.plugins.threatintel.migrations.V20170815111700_CreateThreatIntelLookupTables.MigrationCompleted"})
db.cluster_config.remove({type: "org.graylog.plugins.threatintel.migrations.V20170821100300_MigrateOTXAPIToken.MigrationCompleted"})

db.lut_tables.remove({name: {$in: ["otx-ip", "tor-exit-node-list", "spamhaus-drop", "abuse-ch-ransomware-domains", "whois", "abuse-ch-ransomware-ip"]}})
db.lut_caches.remove({name: {$in: ["spamhaus-e-drop-cache", "otx-ip-cache", "whois-cache", "threat-intel-uncached-adapters"]}})
db.lut_data_adapters.remove({name: {$in: ["otx-ip", "whois", "abuse-ch-ransomware-ip", "tor-exit-node", "spamhaus-drop", "abuse-ch-ransomware-domains"]}})

[kroepke]

The OTX adapter isn't restarted when its configuration is changed on the Overview page.
This unfortunately requires manual work in

graylog-plugin-threatintel/src/main/java/org/graylog/plugins/threatintel/PluginConfigService.java

Line 68 in f50906d

// check for changes in the configuration and bounce the corresponding adapters if something changed

If the adapter is disabled and a lookup is attempted via the table's detail page, an NPE is thrown. This might be a shortcoming of the overall system, probably nothing specific to the OTX adapter.

[bernd]

@kroepke Good catch!

I removed the config setting to disable the OTX adaper because it doesn't need to be disabled/enabled. There is no background data fetching and also the API key is not strictly required.

[kroepke]

With the latest changes it works for me, too.