CCIP-6264 Removing redundant filter for data word > 0x0

[mateusz-sekara]

ExecutionStateChange.State > 0 filter was redundant. It was translated to the following filter in the SQL query

substring(data from 32 * 1 + 1 for 32) > '\x0000000000000000000000000000000000000000000000000000000000000000'

That requires an additional index scan to verify whether the state is greater than or equal to 0. However, events with state = 0 must never land in the logs table, because UNTOUCHED(0) is an internal status used by the contract to track the state of the message during TX.

ExecutionStateChange event must never be emitted with anything other than INPROGRESS(1), SUCCESS(2) or FAILURE(3). Therefore, we can safely assume that extra filtering on the database level is not required. However, to stay defensive, we will add a check that will ignore events containing UNTOUCHED

[github-actions]

Metric	exec-state-filtering	main
Coverage	70.1%	69.6%