chore: restore pending release changesets

[dustinbyrne]

💡 Motivation and Context

The release workflow for posthog-php@4.3.0 partially succeeded: it committed the version bump, but failed creating the GitHub release because the immutable 4.3.0 release/tag already exists.

This restores the two pending changesets and removes the generated duplicate 4.3.0 changelog section while leaving package/composer/library versions at 4.3.0. With those changesets restored, the next release should resolve to 4.4.0 cleanly instead of attempting to recreate 4.3.0.

💚 How did you test it?

Ran:

pnpm changeset status --verbose

Confirmed Changesets reports the next minor release as posthog-php 4.4.0 from the restored changesets.

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

If releasing new changes

• Ran pnpm changeset to generate a changeset file

[dustinbyrne]

Somehow package.json version was out of sync, but it should be working now as it's been resolved:

posthog-php/package.json

Line 3 in a8dc011

"version": "4.3.0",