fix(lint/v2): accept descriptor names for unnamed ABI parameters

[manuelwedler]

Solidity parameters can be left unnamed, so the reference ABI fetched from the explorer carries an empty name and no schema path is computed for them. Descriptors must still name them to reference them by path, which made ValidateDisplayFieldsLinter report a spurious Invalid display field error.

• Fixes 5 errors in the registry: aave/calldata-WrappedTokenGatewayV3.json (#.pool, 4 functions) and 1inch/calldata-AggregationRouterV3.json (#.pools).
• The name is read from the descriptor format key, so the v2 linter interface now also receives the input descriptor (resolution reduces those keys to selectors).
• A name is only accepted at the position it is declared at: the path stays invalid if the reference ABI names that parameter.

Verified on the registry at 3ddfbc0: Invalid display field 5 → 0, all other error and warning counts unchanged.

[fsamier]

Hi @manuelwedler!
Thanks a lot for your multiple contributions!
For full transparency, despite the library being open-source, the workflows have not been designed with external contributor in mind, so we will need to spend some time to adapt them. We have unfortunately higher priority tasks for the moment, but we'll update the workflows and review your PRs as soon as time permits!

[manuelwedler]

Hi @fsamier
Thanks for the quick reply. Just for context, we need these changes for the clear signing registry. Master CI is failing currently because it depends on this library and #308 would fix it. The other two PRs are for fixing and improving the CI jobs which run on new descriptor PRs to the registy.

These changes would be very helpful to move forward with the clear signing registry. The registry has been in a stuck state since the handover which I'm trying to get resolved at the moment.

[fsamier]

Tests run locally with API key injection, workflow to be improved in a later PR