fix(wallet): fix GetTransactionsByStatus for custom chains

[onyb]

GetChainId() only takes known networks into consideration, hence transactions of custom chains are never found. As a result, clients are unable to query and display the pending transaction for signing.

Resolves brave/brave-browser#30642

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

The following scenarios should be tested:

1. As a user I can perform a swap on https://matcha.xyz on the Arbitrum network.
2. As a user I can see the above transaction (before and after approval) in the transaction history.
   i. With "All networks" dropdown selected.
   ii. With "Arbitrum" dropdown selected.

See linked issue for more details.

[srirambv]

Verification passed on

Brave	1.54.16 Chromium: 114.0.5735.53 (Official Build) nightly (64-bit)
Revision	c499d7ea22c8b2dba278465a5df7b86a8efa4e64-refs/branch-heads/5735@{#970}
OS	Linux

• Verified steps from PR
• Verified both unapproved and confirmed transactions are listed under activity tab
• Verified both unapproved and confirmed transactions can be filtered by network

18651.mp4