Expandable UI for Tuples and Bytes in Remix

[CatalinBalut]

Description:
Currently, in Remix IDE, working with function signatures that include complex structs, arrays, or tuples is challenging. Users are required to manually construct these inputs, which can be error-prone and time-consuming. It would be highly beneficial to introduce a feature that allows users to expand tuples and structs directly within the Remix interface.

This feature could include:
-> Expandable Tuple Inputs: When a function parameter is a tuple, users can expand the tuple to input each parameter individually. Remix would then automatically combine these parameters into the required tuple format.
-> Bytes Parameters Support: For parameters that are byte sequences (e.g., bytes), allow users to input multiple fields or values that Remix can combine into the final bytes format. This would eliminate the need to manually construct helper functions for such operations.

Proposed Behavior:
-> When the user encounters a function signature with a tuple, struct, or array, an expandable UI should allow them to input values field by field.
-> For bytes parameters, provide an option to input multiple fields or raw values, which are then combined into the expected format.
Current Workaround:

Users currently have to:
-> Write separate helper functions to construct the tuple or byte arrays in Solidity.
-> Deploy these helper functions or simulate them externally before interacting with the main contract.

Benefits:
-> Streamlines the process of testing and interacting with smart contracts.
-> Reduces errors caused by manual construction of complex parameters.
-> Saves significant development and debugging time.

Example Use Case:
Suppose a function takes a parameter of type tuple(uint256, string, address[]). With this feature, users could expand the tuple, enter values for each field (uint256, string, address[]), and Remix would construct the tuple automatically. Similarly, for bytes, users could input multiple parameters (e.g., a uint256 and string) to form the required bytes sequence.

This feature would make Remix much more user-friendly, especially for developers working with complex contract structures.
cc: @ryestew