Finalize v0.7.0 whatsnew

[RDaxini]

Migrates changelog previously documented in 0.6.2 whatsnew and adds missing entries

[RDaxini]

@martin-springer @tobin-ford please review and add/modify entries however you see fit

#302/#303 needs to be added

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.67%. Comparing base (c423459) to head (1cf1240).

Additional details and impacted files

@@                  Coverage Diff                   @@
##           restructure_notebooks     #304   +/-   ##
======================================================
  Coverage                  74.67%   74.67%           
======================================================
  Files                         41       41           
  Lines                       4813     4813           
======================================================
  Hits                        3594     3594           
  Misses                      1219     1219           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[RDaxini]

Updated the reference according to https://zenodo.org/records/17266145 in order to resolve #283, but I am not sure how we can have the latest stable release referenced in the docs because the zenodo citation doesn't exist until the next release has been pushed. We will always be one behind, unless we update the docs with the new reference without tagging a release? That might mess up the commits ahead/behind of the main branch though. I don't know. @martin-springer ?

[tobin-ford]

I have nothing to add to the whatsnew from my work. My last PRs not associated with the PySAM implementation were captured in v0.6.0.

Not sure about the zenodo issue. Hopefully Martin has some insight.

[martin-springer]

Updated the reference according to https://zenodo.org/records/17266145 in order to resolve #283, but I am not sure how we can have the latest stable release referenced in the docs because the zenodo citation doesn't exist until the next release has been pushed. We will always be one behind, unless we update the docs with the new reference without tagging a release? That might mess up the commits ahead/behind of the main branch though. I don't know. @martin-springer ?

I've addressed the zenodo issues with the notebook refactor and update of the readme's. It does point now to the latest release available.