[CAST-303]Fix SQL geo_ip_data table to accomodate new extra column in GeoLite2-…

[jacobCorsha]

…City-Blocks-IPv4.csv

Before you submit your PR, make sure you check each of the following:

1. I have read the Contributing Guidelines and signed the Contributor License Agreement.
2. My code is clean and ready-to-PR, including being free of lint errors and dead code
3. I have tested my change / code and am confident that it works
4. I have filled in the template below completely and accurately

Changelog

Updated the init.sql file realign the geo_ip_data table to the schema defined by MAXMIND at https://dev.maxmind.com/geoip/importing-databases/postgresql. This reestablished the ability to utlize Maxmind GeoLite2 Data.

Testing

Briefly describe how you are sure your code works, and be sure to include:

1. Ran cast without uploading GeoLite2 CSVs to ensure normal functionality remained
2. Ran cast with ban FEODO Banlist data extension to ensure it was not changed.
3. Ran cast with curl post call to upload GeoLite2-City-Blocks-IPv4.csv checked if things broke.
4. Ran cast with curl post call to upload GeoLite2-City-Locations-en.csv checked if things broke.
5. Ran cast with curl post calls to uplaod both GeoLite2-City-Blocks-IPv4.csv and GeoLite2-City-Locations-en.csv. Examined the outputs to see if it caught and labeled geo_id tagged entities as per expectations.

Unit Tests

N/A

[DavidCorsha]

LGTM, can you add the ticket number to the PR title?

[justincorsha]

Great find! Thanks for fixing up the schema 🚀