Document Vavr collection types as query method parameters

[AzazelSensei]

The Vavr section only talked about return types. Those wrappers are also unwrapped on the way in (ParametersParameterAccessor / QueryExecutionConverters), so findByStatusIn(io.vavr.collection.List) is a regular IN clause.

Fixes #3525

[fResult]

Hi, @AzazelSensei,
Thanks so much for taking this and submitting the PR!

I have a couple of suggestions to make the documentation clearer and cover the items mentioned in the #3525 issue:

1. Refine phrasing in query-methods-details.adoc:L281-283

  That is, a `java.util.List` is turned into a Vavr `List` or `Seq`, a `java.util.Set` becomes a Vavr `LinkedHashSet` `Set`, and so on.

+ These Vavr types are also accepted as query method *parameters* (as of 2.0). If a repository method parameter uses one of the types above (or `Traversable`), Spring Data automatically unwraps it into its Java-native equivalent before executing the query.
+
+ For example, a derived query method declared as `findAllByIdIn(io.vavr.collection.List<Long> ids)` accepts a Vavr `List` and unwraps it to a `java.util.List` so it binds correctly as an `IN`-clause. A Vavr `Option` parameter is similarly unwrapped to its inner value (or `null`).

  The same types are also accepted as query method *parameters*.

2. Update table entry in query-return-types-reference.adoc:L30

- |Vavr `Seq`, `List`, `Map`, `Set`|Vavr collection types. See xref:repositories/query-methods-details.adoc#repositories.collections-and-iterables.vavr[Support for Vavr Collections] for details.
+ |Vavr `Seq`, `List`, `Map`, `Set`|Vavr collection types, also accepted as query method parameters. See xref:repositories/query-methods-details.adoc#repositories.collections-and-iterables.vavr[Support for Vavr Collections] for details.

Let me know what you think.
And thx again for your help! 🙌

[AzazelSensei]

Took your wording. The Vavr section now has the 2.0 unwrap, Traversable, and the findAllByIdIn example. Table row mentions parameters too.