fix: incorrect string concatenation in getFunctionInputKey

[Himess]

Description

This PR fixes an issue in the getFunctionInputKey function where incorrect string concatenation was causing unintended key generation.

Previously, the expression "0_" + abiTupleParameter.name || "tuple" had an incorrect precedence.
As a result, if abiTupleParameter.name was undefined or an empty string, "0_" would be used instead of "tuple", leading to incorrect key generation.

The original code assumes that abiTupleParameter.name can be undefined or an empty string.
If this was never a possibility, then the "tuple" fallback would not have been included in the first place.

If abiTupleParameter.name was always defined and a non-empty string,
then || "tuple" would not be necessary.

However, since "tuple" was included, it indicates that undefined or "" (empty string) is a valid scenario.
The incorrect operator precedence caused "0_" to be used instead of "tuple" in these cases.

Fix

• Updated the expression to ensure the correct fallback value is applied:
  Old: "0_" + abiTupleParameter.name || "tuple"
  New: abiTupleParameter.name ? "0_" + abiTupleParameter.name : "tuple"

This fix ensures that "tuple" is correctly used when abiTupleParameter.name is undefined or empty, preventing potential key mismatches in form handling.

Additional Information

• I have read the contributing docs (if this is your first contribution)
• This is not a duplicate of any existing pull request

Your ENS/address: himess.eth / 0xF46b0357A6CD11935a8B5e17c329F24544eF316F