Update cardano-node changelog

[aniketd]

Description

@jasagredo found the inconsistency that the change-log for cardano-node wasn't kept completely up-to-date and its name wasn't following the convention.

As to "why" this might be: in my under-qualified opinion, I think most likely due to an undocumented technical limitation in our automated operational infrastructure, or second-most likely due to an egregious oversight. If it is indeed the former, I expect this PR to trigger the CI action in question.

In this PR, we update the cardano-node change-log, add a link to it from the top-level change-log, and also update its reference in the respective cardano-node.cabal file.

NOTE: The markdown link checker is expected to fail, since the link will only be valid once we merge this PR

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. These may include:
  • golden tests
  • property tests
  • roundtrip tests
  • integration tests
    See Runnings tests for more details
• Any changes are noted in the CHANGELOG.md for affected package
• The version bounds in .cabal files are updated
• CI passes. See note on CI. The following CI checks are required:
  • Code is linted with hlint. See .github/workflows/check-hlint.yml to get the hlint version
  • Code is formatted with stylish-haskell. See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
  • Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7
• Self-reviewed the diff

Note on CI

If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges. Please contact IOG node developers to do this
for you.

[jasagredo]

In general I think these changes are fine, but I don't know if they are exhaustive. Is it decided that we are keeping track of the changelog for cardano-node then in the file?