Country content: Fix plugin... again

[EricDunsworth]

• Replace all references to freegeoip.app (which stopped working in late April) with country.is and api.country.is
• Rename country_code JSON key to country
• Overview of country.is:
  • Has existed since 2014-2015
  • Site claims not to collect request logs
  • Doesn't have any usage limits according to How many requests can I do? lineofflight/country#17
  • Discovered it in public-apis/public-apis#geocoding
• Successor to Country content: Fix plugin #8928

[EricDunsworth]

Heads up to any reviewers - this plugin caches country codes in local storage via the countryCode key. Might need to delete the key while testing.

[EricDunsworth]

FWIW GitHub Actions' build failures don't seem to have anything to do with this PR's changes.

[EricDunsworth]

I think I've figured out what's up with GitHub Actions...

The Rake step runs HTMLProofer to check links and is currently producing a few dozen errors.

Looks like it first started on July 13th in #9321. Not as a result of anything that changed in the repo, but as a result of HTMLProofer having been updated to v4. An overview of major changes between 3.x and 4.x can be found in its UPGRADING file.

[GormFrank]

Approved upon successful testing.

@BrahimMahadi Please test locally :)

[EricDunsworth]

Just rebased :)! Should start passing in 10-20 mins.

[BrahimMahadi]

What is the path that I need to enter to test this? I can't seem to get it to work. I tried these but I get a "unknown revision or path not in the working tree:
git reset --hard upstream/v4.0-country-content-country.is
git reset --hard upstream/v4.0-country-content-country

[EricDunsworth]

@BrahimMahadi You'll probably need to to add an extra EricDunsworth remote that points to https://github.com/EricDunsworth/wet-boew.git (i.e. my fork of wet-boew/wet-boew), then fetch from it and switch to its v4.0-country-content-country.is branch. That branch doesn't exist in the upstream remote.

[BrahimMahadi]

Tested and everything works fine

[GormFrank]

Thank @EricDunsworth, at least we'll have a working solution even if we decide to eventually switch again.

@BrahimMahadi Thank you for testing!