Revert "meta(changelog): Update changelog for 0.2.3"

[andreiborza]

Reverts #60 because the release didn't go through.. 😅. Trying again.

[andreiborza]

Tbh, not sure what a good workflow should be for these cases...

[Lms24]

The changelog policy for migr8 is currently set to auto in the craft config, meaning the new changelog should have a ## Unreleased section with the new items which will be set to the version by craft during release preparation.

[Lms24]

I vote we either set the policy to simple like in sentry-javascript or add the Danger workflow to get a PR comment to remind us of adding a changelog item. I'd slightly prefer the second alternative because the repo is small enough that adding a changelog entry to the respective PR as opposed to crafting a changelog before the release makes sense IMO. But no strong feelings - feel free to go with whatever you prefer

[Lms24]

Feel free to merge this or change ## 0.2.3 to ## Unreleased (see my comment)