Changelog: prepare for the release of version 2.0.0

[enricobattocchi]

The release date has been tentatively set to next Thursday, December 28, 2023.

[jrfnl]

@enricobattocchi Looks good.

I wonder if the following things should also be mentioned:

• That the plugin is now tested up to PHP 8.3.
• PR 132 whip php 81 improvements #133 - Improved PHP 8.1 compatibility (PRs Whip_MessageDismisser::verifyNonce(): bug fix #144 and Whip_WPMessageDismissListener::listen(): bug fix #145 are follow ups on this and fix new bugs introduced by 132 whip php 81 improvements #133, so don't need a explicit mention).
• PR Whip_WPMessagePresenter: remove deprecated method #158 - Removed method.

[enricobattocchi]

* That the plugin is now tested up to PHP 8.3.

Right! Pushed.

* PR [132 whip php 81 improvements #133](https://github.com/Yoast/whip/pull/133) - Improved PHP 8.1 compatibility (PRs [Whip_MessageDismisser::verifyNonce(): bug fix #144](https://github.com/Yoast/whip/pull/144) and [Whip_WPMessageDismissListener::listen(): bug fix #145](https://github.com/Yoast/whip/pull/145) are follow ups on this and fix new bugs introduced by [132 whip php 81 improvements #133](https://github.com/Yoast/whip/pull/133), so don't need a explicit mention).

#132 is not actually about PHP 8.1 compatibility I think? We removed the undesirable filter_input occurrences but they weren't actually deprecated since they weren't using any FILTER_SANITIZE_*... so maybe it's not worth mentioning?

* PR [Whip_WPMessagePresenter: remove deprecated method #158](https://github.com/Yoast/whip/pull/158) - Removed method.

Right, pushed.

[jrfnl]

• PR 132 whip php 81 improvements #133 - Improved PHP 8.1 compatibility (PRs Whip_MessageDismisser::verifyNonce(): bug fix #144 and Whip_WPMessageDismissListener::listen(): bug fix #145 are follow ups on this and fix new bugs introduced by 132 whip php 81 improvements #133, so don't need a explicit mention).

#132 is not actually about PHP 8.1 compatibility I think? We removed the undesirable filter_input occurrences but they weren't actually deprecated since they weren't using any FILTER_SANITIZE_*... so maybe it's not worth mentioning?

Well, maybe it is worth mentioning as "security hardening" as no filter was being passed previously, which meant that FILTER_DEFAULT was used, which basically meant that the input was not being sanitized.... ?

[enricobattocchi]

Well, maybe it is worth mentioning as "security hardening" as no filter was being passed previously, which meant that FILTER_DEFAULT was used, which basically meant that the input was not being sanitized.... ?

Makes total sense, pushed

[jrfnl]

LGTM!