Listing resolver states in `LocatableResolverBackedStore`s ignores execute state in scan properties

[alecgrieser]

The LocatableResolverBackedStore (which presents a façade in front of a LocatableResolver (a generalization of the directory layer) that allows it to be accessed via the JDBC interface) has a method for scanning the "resolver states" associated with its underlying resolver. That scan method currently ignores the "execution state", which in turn means that it won't ever contribute to the number of rows scanned by the database, so a (mostly hypothetical and far-fetched) scenario where someone asked to limit the number of rows read by the database and then proceeded to scan the resolver state record (which is limited to one per directory layer) in a tight loop wouldn't get the out-of-band limit they expected.