Match logic of balance badge to format max input value

[jinchung]

Fixes APP-1627

What changed (plus any additional context for devs)

1. The formatting for max input value was using the valueBasedDecimalFormatter which is slightly different from the logic that the balance badge uses. This PR ports over the essential logic of the balance badge into a worklet and uses that for formatting.
2. This also fixes an issue with the non-worklet handleSignificantDecimals function that was copied over from helpers/utilities. A comment is added inline below describing the issue.

What to test

• Tap max on various input assets (native and non-native) across multiple networks.
• For non-native assets, the max formatted input value should match the balance badge.
• For native assets, the max formatted input value should look similarly formatted to the balance badge, though the max input amount will be slightly less than what is shown in the balance badge since it needs to account for gas + some buffer.

Screen recordings / screenshots

[linear]

APP-1627 Align the decimal formatting logic for max with the same one used for max balance

[jinchung]

fixing this as this was copied over incorrectly from the original helpers/utilities file: https://github.com/rainbow-me/rainbow/blob/develop/src/helpers/utilities.ts#L217

this line was ignoring the result of line 171 where it finds the index of the first significant (non-zero) digit and adds a buffer.