Release prep v8.0.0

[github-actions]

Automated release-prep through pdk-templates from commit 5656cdb.
Please verify before merging:

• last nightly run is green
• Changelog is readable and has no unlabeled pull requests
• Ensure the changelog version and metadata version match

[h0tw1r3]

@bastelfreak @smortex I'm going back and forth on if a major version bump should be done, because of the firewall module bump and platform support drops.
And if it is a major release, should the postgresql module bump be included also?

[bastelfreak]

100% this is a major release and should be 8.0.0. And we should include #379

[bastelfreak]

Do we have to rewrite the whole changelog? I think this project uses not the github changelog generator? That allows to put the old changelog in a HISTORY.md and keep it. Makes the diff way more readable.

[h0tw1r3]

fixed

[smortex]

Re-opening, see #399

[smortex]

Oh crap, the changelog is not generated with the rake changelog task 😒.

I recall triaging all issues in various modules, so I guess we want to do this too for consistency? The current tooling will then generate a full changelog without HISTORY.md on each release, but as the HISTORY.md contain the old changelog, maybe it will not be too bad?

[smortex]

I labelled issues, and regenerated CHANGELOG.md by hand (because it is not currently in the main branch so the GitHub action does not think it must be updated). This is a PITA only for this release as the next ones will not have this corner case.

[zilchms]

Should there be a release after #395 is merged or are there still things that should be waited on?

[bastelfreak]

I wanted to regenerate the CHANGELOG.md, but this fails: https://github.com/puppetlabs/puppetlabs-puppetdb/actions/runs/8642538232/job/23693810562

[smortex]

I wanted to regenerate the CHANGELOG.md, but this fails: puppetlabs/puppetlabs-puppetdb/actions/runs/8642538232/job/23693810562

Looks like there was some issues in the pdk templates that got fixed.

[smortex]

I guess we want to merge this one: #357