eth/filters, cmd: add config of eth_getLogs address limit

[hlongvu]

Add cli configurable limit for the number of addresses allowed in eth_getLogs filter criteria: #32264

Key changes:

• Added --rpc.getlogmaxaddrs CLI flag (default: 1000) to configure the maximum number of addresses
• Updated ethconfig.Config with FilterMaxAddresses field for configuration management
• Modified filter system to use the configurable limit instead of the hardcoded maxAddresses constant
• Enhanced test coverage with new test cases for address limit validation
• Removed hardcoded validation from JSON unmarshaling, moving it to runtime validation

Please notice that I remove the check at FilterCriteria UnmarshalJSON because the runtime config can not pass into this validation.

Please help review this change!

[rjl493456442]

Very solid work, thanks for your contribution!

Just one nitpick, please fix it.

[rjl493456442]

nitpick, please use ethconfig.Defaults.FilterMaxAddresses

[hlongvu]

thanks, I've updated the PR

[zsfelfoldi]

It is not logical to limit the number of addresses but not limit the number of topic alternatives at each topic position (topics is a 2D array and maxTopics only limits one dimension). They can cause similar extra load to the search algorithm so I'd just introduce a single limit that applies to both the address field and each of the topic positions. I have no good idea though on how to name this flag.
Otherwise this PR could be good, should be fairly easy to add checks for the topics too. Please do not merge though until we figure out how these constraints should exactly look like and what we should name the flag.

[s1na]

I have no good idea though on how to name this flag.

@zsfelfoldi what do you think about maxCriteria or maxQueryOptions? We can explain it more in the flag description. Another is queryBudget.