feat: support new parameters for KeyValueStore.listKeys

[barjin]

Recent changes in Apify API added ?prefix= and ?collection= query params to the KVS /keys endpoint. We should add these to Crawlee's interfaces (and likely support this in MemoryStorage-based KVS too to keep the parity).

Motivation

parity / enabling new features from Apify API

Ideal solution or implementation, and any additional constraints

Expand the interfaces with prefix?: string and collection?: string fields. Implement a simple startsWith filter in MemoryStorage KVS implementation (for prefix). See below for collection.

Other context

While the implementation of the prefix filter is quite straightforward, I'm not sure about the collection parameter. It seems like higher-level logic and deeper investigation (whether we should / shouldn't implement this) is required.