Ci/automate updating the CHANGELOG.md files

[ellet0]

Description

This PR aims to update #1878 changes to also automate the generation of the CHANGELOG.md files, the maintainers are no longer required to manually change the version.dart and the root CHANGELOG.md then run the script, and after that commit the changes and push them, then create a Github release to automate the publishing

now, you just have to create a new GitHub release, you can use the auto-generate release notes button or manually type the changes and once you click the publish button, the CI will automate this whole process, I migrated all the previous data from CHANGELOG.md to CHANGELOG.json (using another quick script that's not in the project)

Don't get confused by this:

It's mostly due to auto-generated CHANGELOG.md files, this PR doesn't change much other than the GitHub workflow, the script, the development notes, and a few changes, I should have let GitHub actions run the script instead but it will be overwritten and doesn't matter that much,

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
• All existing and new tests are passing.
• I have run the commands in ./scripts/before_push.sh and it all passed successfully

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[ellet0]

Since I wasn't able to test the changes locally using act or other solutions, I should have tested the changes and tested the publishing workflow in this branch directly instead of the master branch