feat: added ReactNode support for KeyValueRow tooltip and label

[Matt561]

Description

Iterates on the <KeyValueRow /> component by adding ReactNode support for tooltip content and label. This should allow for greater flexibility using <KeyValueRow />.

Related issues

These are prerequisite changes needed in mobile native staking tickets. (e.g. STAKE-824: [FE] Build staking input confirmation screen)

Manual testing steps

1. Open the storybook
2. Select <KeyValueRow /> inside of components-temp directory

Screenshots/Recordings

Before

Missing bottom example using ReactNode (Button Link)

After

Has bottom example that's using ReactNode (Button Link)

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[georgewrmarshall]

LGTM! Approving to unblock but @brianacnguyen may be a better resource for review.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
78.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b126022
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d7bff9eb-24ca-4458-b195-18c61b2d2221

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise