FEAT: Introduce IdentifierFilters to allow generic DB queries on identifier…

[behnam-o]

1. Introduce IdentifierFilters which allow us to query memory entities by matching properties of their referenced identifiers
2. Replace some existing identifier-based queries with the new generic functions
3. Add tests
4. [stretch but along the same lines] introduces a few similar internal methods that operate on identifiers, abstracting the entity specificities from DB interface implementations (for example, we have a method on the interface to get unique values out of an array that holds converter classes, found somewhere in an attack identifier property. Today, each implementation of memory (AzureSQL/SQLite) has a hard-coded query that does only that by explicitly referencing the attack result table, doing some json magic, and extracting the values. With these new methods, the interface requires the implementations to implement mechansims to extract unique values out of any array in a JSON column, so 1) they don't need to hard-code queries on specific component types and 2) it can be reused on any desired property/identifier without having to update the memory implementations

[ValbuenaVC]

This PR (#1451) might be a useful reference since it also handled filtering concerns, although for datasets.