Expose Location information

[juzuluag]

Issue Number: (microsoft#229, microsoft#214, #175)

Summary

Expose Locations data through all the 'user's' interfaces (WebApi, CLI, GSF SDK)

Changes

• Add new WebApi route /locations
• Add new CLI option caw locations
• Add new GSF.CarbonAware API handler ILocationHandler

Checklist

• Local Tests Passing?
• CICD and Pipeline Tests Passing?
• Added any new Tests?
• Documentation Updates Made?
• Are there any API Changes? If yes, please describe below.

Are there API Changes?

If yes, what are the expected API Changes? Please link to an API-Comparison workflow with the API Diff.

• WebApi route /locations
• CLI option caw locations
• GSF.CarbonAware API handler ILocationHandler.GetLocationsAsync

Close #175

[codecov-commenter]

Codecov Report

Merging #239 (349a65e) into dev (67b46c8) will decrease coverage by 0.64%.
The diff coverage is 56.92%.

@@            Coverage Diff             @@
##              dev     #239      +/-   ##
==========================================
- Coverage   76.74%   76.09%   -0.65%     
==========================================
  Files          71       73       +2     
  Lines        2283     2334      +51     
  Branches      230      234       +4     
==========================================
+ Hits         1752     1776      +24     
- Misses        468      495      +27     
  Partials       63       63              

Impacted Files	Coverage Δ
...e/src/Configuration/ServiceCollectionExtensions.cs	0.00% <0.00%> (ø)
...rc/GSF.CarbonAware/src/Handlers/LocationHandler.cs	0.00% <0.00%> (ø)
src/GSF.CarbonAware/src/Models/Location.cs	0.00% <0.00%> (ø)
...re.WebApi/src/Controllers/CarbonAwareController.cs	95.29% <83.33%> (-0.96%)	⬇️
.../CarbonAware.LocationSources/src/LocationSource.cs	86.25% <100.00%> (+5.92%)	⬆️

[JenMadiedo]

This is a cool solution, thanks for the taking the time to do it all. I had one quick question about how the user will know about the duplicated key situation

[vaughanknight]

This is awesome, let me know when it's ready for us to review. We had been looking at this for a while and it came up in the hackathon to document on the website the locations, but we had decided that a service would be better to get the data live.

For these named locations however, should we also be doing forecast?

[juzuluag]

This is awesome, let me know when it's ready for us to review. We had been looking at this for a while and it came up in the hackathon to document on the website the locations, but we had decided that a service would be better to get the data live.

For these named locations however, should we also be doing forecast?

Hi @vaughanknight, thank you for pointing this out. The WebApi route should be /locations. This is something that I'll fix. It would be in sync with the CLI and GSF.CarbonAware.
W/r/t forecast, it will be independent whether is emissions or forecast.

[JenMadiedo]

Looks great, thanks for the comment

[juzuluag]

@vaughanknight ready for review

[vaughanknight]

Very happy with this one. Thank you very much. We may look a changing the response type maybe but I want to get it into dev as we feel it's best if we get some people using it and get feedback before it goes into main. Thanks again!