Modifies temperature, precipitation, and taspr routes to not use a wildcard for the endpoint.

[BobTorgerson]

This PR expands the route definitions for temperature, precipitation, and taspr to no longer have a wildcard "catch all" start to the endpoint. Without this change, any non-existent endpoint that ends in point// or area/ was resolving to these endpoints and causing an uncaught error to appear in Varnish (HTTP 503 error).

Example failure:

https://earthmaps.io/foo/bar/point/65/-156

If you run this code, and attempt that endpoint, it correctly gives a "bad request" error message:

https://localhost:5000/foo/bar/point/65/-156

Ensure that you can still get access to the temperature, precipitation, and taspr endpoints for both lat / lon and area summaries.

https://localhost:5000/temperature/point/65.0628/-146.1627
https://localhost:5000/precipitation/point/65.0628/-146.1627
https://localhost:5000/taspr/point/65.0628/-146.1627

https://localhost:5000/temperature/area/19010208
https://localhost:5000/precipitation/area/19010208
https://localhost:5000/taspr/area/19010208

[kyleredilla]

Yeah I see what's going on here, looks like these changes will fix the issue. Tested with supplied links in PR and cross-checked values with production API, things look good. Approved.

[charparr]

Hey this looks good! I'm testing the suggested endpoints and a few others and not hitting any issues - they work as expected for both cases where I anticipate a 503 and where I expect to get data. This PR will make it easier for us to test / develop new endpoints because we won't get misled by the mysterious guru meditation when in reality all we did was goof route the name. Like temprature which I type more than I'd like to admit. Thanks Bob!

[charparr]

Closes #350