Add support for list query arguments

[rorbech]

This adds support for passing any Iterable as list arguments to the RQL IN operator.

realm.query<QuerySample>("intField IN $0", listOf(1, 3))
realm.query<QuerySample>("intField IN $0", settOf(1, 3))
realm.query<QuerySample>("intField IN $0", 1 .. 3 step 2)

Input for review
I took some shortcuts for handling allocation and assignments of lists for query arguments. It is not as efficient as it could be, but given that we might want to tweak our scheme for transferring values to the C-API if we can generate the code, I chose to fix support for list arguments and will leave the optimizations for later. The current C-API wrappers does not offer identical was to work with lists of contiguous value types. It didn't find a uniform way to allocate a list of element and then update the elements in place with the current wrapper frameworks. Swig's array_functions copies values when accessed by index whereas Kotlin Native's cinterop only allows you to work with the element by reference. As our overall converter infrastructure is currently creating instances and passing it around, it was easier to just memcpy the elements into place in Kotlin Native than reworking the whole infrastructure to assign native references on JVM (and that would also not allow us to use the generated Swig array-functions for valueArray).

Closes: #929

[cmelchior]

Awesome... I can see why this is a bit suboptimal, but given that this code doesn't run in any hot path, it is probably okay 👍

[cmelchior]

I don't think we need to be exhaustive here, but it would be nice with a test for this that takes objects as arguments, just as a smoke test since it involves are few more moving parts.

[cmelchior]

Actually we also need to test strings with ' and "

[rorbech]

I have added and extended some test cases (list with single element, strings and objects) in f82058e#diff-db6b549cfdb4b7e0512e5d470bdd52902d32f0647ff5d9b8e1a9f72b7b952546 but some fail, so will have to await resolution of core issues.

[rorbech]

Still fails for object links. Created realm/realm-core#6688 to track that.

[cmelchior]

This is now waiting for realm/realm-core#6705 to be merged.

[rorbech]

realm/realm-core#6705 has been merged, so should try to update core. There seem to be a number of API changes, so not just a submodule update though.