Update CHANGELOGs

[Lucsanszky]

Description

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated
• When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
  versioning process.
• The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
• All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
• Code is formatted with fourmolu (use scripts/fourmolize.sh)
• Cabal files are formatted (use scripts/cabal-format.sh)
• hie.yaml has been updated (use scripts/gen-hie.sh)
• Self-reviewed the diff

[teodanciu]

Looks good to me, but I think that after we release cardano-ledger-babbage-test 1.2.0.2 and cardano-ledger-conway-test 1.2.1.5, after your other PR gets merged, we also need to add a changelog entry for their corresponding cabal files

[Lucsanszky]

Looks good to me, but I think that after we release cardano-ledger-babbage-test 1.2.0.2 and cardano-ledger-conway-test 1.2.1.5, after your other PR gets merged, we also need to add a changelog entry for their corresponding cabal files

Will do! As soon as the CHaP release is done and I pushed the tags here. Until then, I'll mark this as draft. Thanks! Done.