fix: account parser in claim fee request

[Cifko]

Description

Allow the account to be parsed from string

Motivation and Context

Upon some testing I came to this issue.

How Has This Been Tested?

In my testing environment I'm doing claiming fees, and I was able to claim them successfuly.

What process can a PR reviewer use to test or verify this change?

You can try to call the jrpc with string and you will see an error without this change.

Breaking Changes

• None
• Requires data directory to be deleted
• Other - Please specify

[github-actions]

Test Results (CI)

72 tests   - 121   70 ✅  - 122   43m 49s ⏱️ - 30m 57s
16 suites  -  36    0 💤 ±  0 
 1 files    -   1    2 ❌ +  1 

For more details on these failures, see this check.

Results for commit bbca0da. ± Comparison against base commit 516c5d1.

This pull request removes 121 tests.

Scenario: Claim and transfer confidential assets via wallet daemon: tests/features/wallet_daemon.feature:89:5
Scenario: Claim base layer burn funds with wallet daemon: tests/features/claim_burn.feature:6:3
Scenario: Claim validator fees: tests/features/claim_fees.feature:6:3
Scenario: Confidential transfer to unexisting account: tests/features/transfer.feature:163:3
Scenario: Counter template registration and invocation: tests/features/counter.feature:7:3
Scenario: Create account and transfer faucets via wallet daemon: tests/features/wallet_daemon.feature:7:5
Scenario: Create and mint account NFT: tests/features/wallet_daemon.feature:133:5
Scenario: Create resource and mint in one transaction: tests/features/nft.feature:73:3
Scenario: Double Claim base layer burn funds with wallet daemon. should fail: tests/features/claim_burn.feature:44:3
Scenario: Indexer GraphQL requests events over network substate indexing: tests/features/indexer.feature:118:3
…