Updated Default PV Resource Data for Non-CONUS Locations

[adfarth]

We have changed the way REopt determines which solar resource dataset to utilize in the PVWatts API call, which is how REopt estimates solar PV production for a given location.

• Before: REopt utilized defined lat-long bounds to determine if the NSRDB or "International" data should be used in PVWatts call (see "dataset" field here: https://developer.nrel.gov/docs/solar/pvwatts/v8/).
• Now: REopt calls the Solar Dataset Query API (v2) (https://developer.nrel.gov/docs/solar/data-query/v2/) to determine the dataset to use, and includes "tmy3" as an option, as this is currently the best-available data for many locations in Alaska. So, if NSRDB data is available through the PVWatts API for the site location, it will be utilized. This change does not affect locations within the contiguous US (CONUS), but may improve the resource data utilized in REopt runs for sites in Alaska or international locations.

If you are using the REopt codebase, you can now see the name of the PV and/or temperature datasource used in your run as an @info message (along with the distance from the site to the datasource location). You will also receive a warning if the data is not from the NSRDB or if the data is more than 200 miles away.