Stop checking for last node in Snapshots

[onufer]

What is the change?

Stop checking if its the last node since this often breaks for snapshots and just calculate reactivity swing at all nodes.

Why is the change being made?

If you do snapshot and don't have cycles and nodes consistent, you get an error.

Cycles and nodes don't have meaning for snapshots, so it is probably best to not force this and calculate partial cycle reactivity swing.

see #2034

SCR Information

Change Type: features

One-Sentence Description: Stop checking if its the last node since this often breaks for snapshots and just calculate reactivity swing at all nodes.

One-line Impact on Requirements: NA

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify any new/changed code.
• The code style follows good practices.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in pyproject.toml.

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity in the last 100 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.