Fix #111, epsg api change

[EricSoroos]

Fixes #111

• epsg.io query interface has changed to maptiler, which requires an api key
• We're only using the proj4 rendering, so there's a different api that's still open/free
• Also adding additional representation of 4326 coordinate system seen in the wild.

[EricSoroos]

Two issues -- I've had the .proj4 url fail in testing, and I've got some more interesting issues axis ordering and the change for the long specification of the SRS.

[amercader]

@EricSoroos How can I test this? Can you share a service/dataset in a non 4326 crs that I can use to test it?

Alternatively we could add a mechanism to include extra proj4js definitions via config if they are known beforehand, but it's worth trying to fix the automated mechanism

[EricSoroos]

There's more going on here that I need to fix up:

• What I was doing I actually was trying to sort for a version of the EPSG 4236 that wasn't recoginzed.
• There's a lot more going on with the EPSG 4326, because this extension is pinning a super old WFS and GML standard.
  The upstream I was using didn't support the older versions, so I have to take what comes there.
• There are multiple ways of specifying the 4326 CRS, and some of them indicate lat/lon and some indicate lon/lat. I think that a lot of the legacy WMS parsing and sniffing can probably just go away, as standards have clarified and moved on from what was done like 12 years ago.

The trouble I have here is one of making sure that the changes work outside of the one (known to be odd for other reasons) upstream.