fix: pass arguments for the contract functions in the correct order

[tx-nikola]

What ❔

This PR fixes the bug where the contract function arguments are not passed in the correct order.

Why ❔

In order to call the contract functions correctly, we need to pass the arguments in the right order.

Explanation

The issue was that we were trying to get Object.entries(params) without actually sorting it, so, for example, contract 0xE1D6A50E7101c8f8db77352897Ee3f1AC53f782B, the revokeRole function asks for [role, account] arguments to be passed.
In the form object, it looks like this:

{
  account: "0xExample",
  role: "0xExample
}

and when we run Object.entries(params) we always get it like this:

[
  ["account", "0x969Bb8Ae65602B4F8f9B459a11084e591c4491C7"],
  ["role", "0x03c321230b026fb61a5a21f62c5f618751ec6d8435327f673bae5bfa570e5879"]]
]

and later after we map it, it becomes ["0x969Bb8Ae65602B4F8f9B459a11084e591c4491C7", "0x03c321230b026fb61a5a21f62c5f618751ec6d8435327f673bae5bfa570e5879"] - swapping the arguments from their intended places.

This issue was happening when someone types the account first, therefore forms become

{
  account: "0xExample",
  role: "0xExample
}

instead of

{
  role: "0xExample,
  account: "0xExample"
}

thus messing up the order of the arguments in the function call.

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.

[github-actions]

API E2E Test Results

207 tests   207 ✅  21s ⏱️
 14 suites    0 💤
  1 files      0 ❌

Results for commit 1de8844.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Results

    4 files    263 suites   11m 35s ⏱️
2 125 tests 2 124 ✅ 1 💤 0 ❌
2 337 runs  2 336 ✅ 1 💤 0 ❌

Results for commit 1de8844.

♻️ This comment has been updated with latest results.

[github-actions]

Visit the preview URL for this PR:
https://staging-scan-v2--pr-347-6chskmeh.web.app