fix(purevpn/updater): parse country and city from hostname and merges with ip address information

[mlapaj]

Description

• The original updater fetches servers from the zip file and checks geo-location of each server IP address. This is not working correctly for virtual servers.
• Some VPN servers have incorrect geolocation data

Assertions

• I am aware that we do not accept manual changes to the servers.json file
• I am aware that any changes to settings should be reflected in the wiki

[qdm12]

I have updated them. We should consider to provide a way to update certificates and keys instead of hard-coding them.

Where did you get them from? Any publicly available source for them?

[mlapaj]

I have updated them. We should consider to provide a way to update certificates and keys instead of hard-coding them.

Where did you get them from? Any publicly available source for them?

This was taken from the zip file - Recommended-CA2.zip. See certificates.

[qdm12]

A few changes done:

• openvpn config changes moved out of PR to have a focused PR. I did push those value updates to the master branch attributing you credits in the commit message
• added missing country codes and city codes in the mapping
• use country-city codes together to determine city name, because there could be ukl and usl for example (ugh lazies purevpn!)
• it tries to parse the country and city from the hostname. If it succeeds, it uses the region from the ip info data ONLY if the country and city more or less match what we parsed.
• if parsing the hostname fails, it uses the country and city from the ip info data
• on the master branch, I also pushed a change where the ip data fetcher now merges "cleverly" ip data from different sources, to have a more reliable country, city etc.

[qdm12]

Also, when it comes to keys/certificates etc. these should not change. It's poor practice to just deprecate these without a every early warning as well. PureVPN is just meh so they changed all their keys/certs/etc. out of nowhere.