Craft a solution for a 'centralized' changelog for the fuels package

[Dhaiwat10]

Currently, the CHANGELOG.md at the root of our project is a symlink that points to the CHANGELOG.md file inside of the fuels package. Apart from the fact that GitHub does not handle symlinks properly, and instead shows this:

... the CHANGELOG.md file inside the fuels package also does not contain all the changes that are incorporated in our codebases. It only includes information about version bumps to other packages.

Ideally, we should have a CHANGELOG.md file at the root of the repo where we append any and all the changes we add to any of the child packages' changelogs.

The motivation behind this is to make it easy for SDK users to browse through our version history and see what changes happened when.

[camsjams]

The changelog should just reference the GitHub releases page, which has the best source of truth and is automated:
https://github.com/FuelLabs/fuels-ts/releases

[arboleya]

I agree, but I also like the idea of a consolidated Changelog.

Perhaps a combination of all could involve:

1. Improve the Changelog template (patch changes seems useless)
2. Add a link to the Releases page at the very top of it
3. Have a consolidated <repoRoot>/CHANGELOG.md with the all releases combined (probably auto-generated)

[arboleya]

Related:

• Write manual release notes for important releases #1347

[arboleya]

This should be automatically resolved by:

• Consider merging all packages into fuels #2493