Handle complex paths in stix filtering resolution and use it consistently

[labo-flg]

This issue is purely technical, and aims at improving our code base reliability and consistency regarding stix object filtering (the internal mechanism we use everywhere, namely the utility function isStixMatchFilterGroup).

in filtering-reosolution.ts:buildResolutionMapForFilter the STIX_RESOLUTION_MAP_PATHS contains mappings between the requested filter key and the key that should be compared in the stix object.

This is very limited, and does not cover the complex case of connectToId filter key, that should search in the stix extension extensions[STIX_EXT_OCTI].id.

1) We need to be able to define complex paths in this mapping

Also, the mapping is not used in the individual testers function, that basically hardcode the same mapping

2) use the mapped (complex) paths in the individual testers for a more robust code