Release v1.7.0

[PaulRotmann]

This pull request updates the changelog and documentation for the upcoming release.

[clue]

@PaulRotmann LGTM, let's get this shipped!

[clue]

For future reference, we're still working out this PR release workflow and this marks the first time I've created a release + tag using GitHub's UI for this release right after merging this PR here.

Unfortunately, GitHub apparently only creates a lightweight tag and not an annotated tag, which in turn goes against git best practices:

Annotated tags are meant for release while lightweight tags are meant for private or temporary object labels. For this reason, some git commands for naming objects (like git describe) will ignore lightweight tags by default.

— https://git-scm.com/docs/git-tag

This has been reported to GitHub a while ago and doesn't look like something that's going to change anytime soon (https://github.com/orgs/community/discussions/4924).

I've created an annotated tag locally and force-pushed this over the lightweight tag to fix this. Not ideal (https://www.reddit.com/r/git/comments/45qpg8/is_it_considered_bad_practice_to_replace_a/), but both tags should point to the same source commit 0b6b9b0.