Create Release Notes for 1.7

[danuw]

What happened?

Create a PR with updated change log.
Will look for PRs and Issues since last release.

Please feel free to add anything missing in the comments...

I used the following commands to help

gh pr list -R Green-Software-Foundation/carbon-aware-sdk --search "-label:agenda label:v1.7 is:closed " --json number,title,url --template \
        '{{range .}}{{ printf "\n-[PR #%v]" .number | autocolor "green"}} {{.title}} {{ printf "](%v)" .url}}{{end}}'

gh issue list -R Green-Software-Foundation/carbon-aware-sdk --search "-label:agenda label:v1.7 is:closed" --json number,title,url --template \
        '{{range .}}{{ printf "\n-[#%v]" .number | autocolor "green"}} {{.title}} {{ printf "](%v)" .url}}{{end}}'

Code of Conduct

• I agree to follow this project's Code of Conduct

Feature Commitment

• I commit to contributing this feature as a PR and working with the GSF to merge this feature into the Carbon Aware SDK.

[danuw]

-[PR #597] Add Client API documents for WebAPI 1.0.0 ](#597)
-[PR #591] Publish WebAPI client library for NPM ](#591)
-[PR #588] Add gh cli to devcontainer/codespace ](#588)
-[PR #471] Add GHA workflow for generating WebAPI client library for Java ](#471)

-[#571] [Bug]: Cannot get the value of a token type 'Null' as a number ](#571)
-[#570] [Bug]: webapi query on bylocation shows 24 hours worth of data even when smaller range requested ](#570)

[danuw]

Should I create a blog post for 1.6.1 too? Apart from that this should be ready to approve @vaughanknight @YaSuenag

[YaSuenag]

I don't understand the positioning of this blog. Does this (almost) copy of a release note? or should blog post create in each major release?

In general as a developers' blog, we should create the post in each releases includes patch release - it means we should create the post for v1.6.1 .

[danuw]

Sounds good to me. Yes for some reason I had missed it and thought if I include with the release notes given it is the same content, it makes most sense.
I will catch up on the 1.6.1 release blog post too to update this PR.

Let me know if any comments / anything missing from release notes in the meantime.

Thank you @YaSuenag