[LW-11922] Update cardano-node to 10.1.3

[michalrus]

LW-11922

This PR updates cardano-node to the latest release, 10.1.3.

It is required that users upgrade to this version of the node.

Todos

n/a

Screenshots

n/a

Testing Checklist

n/a, will be done together in a release branch.

Review Checklist

Basics

• PR assigned to the PR author(s)
• input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
• If there are UI changes, Alexander Rukin assigned as an additional reviewer
• PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
• PR link is added to a Jira ticket, ticket moved to In Review
• PR is updated to the most recent version of the target branch (and there are no conflicts)
• PR has a good description that summarizes all changes
• PR contains screenshots (in case of UI changes)
• CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
• There are no missing translations (running yarn manage:translations produces no changes)
• Text changes are proofread and approved (Jane Wild / Amy Reeve)
• Japanese text changes are proofread and approved (Junko Oda)
• Storybook works and no stories are broken (yarn storybook)
• In case of dependency changes yarn.lock file is updated

Code Quality

• Important parts of the code are properly commented and documented
• Code is properly typed with typescript types
• React components are split-up enough to avoid unnecessary re-renderings
• Any code that only works in main process is neatly separated from components

Testing

• New feature/change is covered by acceptance tests
• New feature/change is manually tested and approved by QA team
• All existing acceptance tests are still up-to-date
• New feature/change is covered by Daedalus Testing scenario
• All existing Daedalus Testing scenarios are still up-to-date

After Review

• Update Slack QA thread by marking it with a green checkmark

[szymonmaslowski]

LGTM, Just one question.

[szymonmaslowski]

Do we need to inform users about the previous node version update? The newer version anyway overrides the previous one.

[michalrus]

I don't know, but I though I'd find it confusing as a user, so I removed the mention of the previous one. ^^ We can revert, if needed.

[DominikGuzei]

yeah i would remove it, only show the version we are releasing in the final build 👍