Reference:

• Ethereum JSON-RPC spec for eth_getLogs:
  https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_getlogs

• Current Starknet JSON-RPC spec for starknet_getEvents:
  https://github.com/starkware-libs/starknet-specs/blob/master/api/starknet_api_openrpc.json#L1173-L1197

Current starknet_getEvents filters are too restrictive. This is currently painful for many indexer use cases. For example, when dealing with factory-deployed contracts, indexers currently must make N separate requests to get child contract events. This could make running a Starknet indexer significantly more expensive compared to an EVM indexer.

Could we allow address to accept either a single address OR an array of addresses? When an array is provided, events from any of the specified addresses would be returned, matching the same functionality as eth_getLogs !