[DDW-1110] Use Vasil-supported cardano-wallet

[michalrus]

This PR uses Vasil-supported cardano-wallet.

For now, this means:

• https://input-output-rnd.slack.com/archives/C02DTDJFW2Z/p1655126708938819
• branch anviking/ADP-1744/node-1.35 = this PR: Update to cardano-node 1.35-rc2 cardano-foundation/cardano-wallet#3280
• branch node-1.35-rc3 = this PR: Update to cardano-node 1.35-rc3 cardano-foundation/cardano-wallet#3340
• branch node-1.35-rc4 = this PR: Bump cardano-node dependency to 1.35.0-rc4 cardano-foundation/cardano-wallet#3349
• official cardano-wallet https://github.com/input-output-hk/cardano-wallet/releases/tag/v2022-07-01, and official cardano-node https://github.com/input-output-hk/cardano-node/releases/tag/1.35.0

Todos

• Switch to proper cardano-wallet release — for now we’re using a preview

Screenshots

Testing Checklist

• Slack QA thread
• Test
• Test Document

---

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
• All visual regression testing has been reviewed (assign run Chromatic label to PR to trigger the run)
• 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

[miorsufianiohk]

LGTM. Great work @michalrus . Tested on 21918 and 21938 👍