[TRACKING ISSUE] Ability to specify multiple partitions in a predicate query (redux)

The tracking issue for the Java side PR.

See https://github.com/hazelcast/hazelcast/pull/21319 for details.

---

This is a redux of [PR-18171](https://github.com/hazelcast/hazelcast/pull/18171). I'm continuing on from @ashley-taylor.

I've gone with a slightly different approach of making a backwards compatible change to the existing `PartitionPredicate` interface (instead of making an entirely new interface). This seemed lower risk as existing code with single partition keys will continue to work, while anything new can take advantage of the `getPartitionKeys` method.

Breaking changes (list specific methods/types/messages):
* PartitionPredicateImpl constructor

Checklist:
- [x] Labels (`Team:`, `Type:`, `Source:`, `Module:`) and Milestone set
- [ ] Label `Add to Release Notes` or `Not Release Notes content` set
- [ ] Request reviewers if possible
- [ ] Send backports/forwardports if fix needs to be applied to past/future releases
- [ ] New public APIs have `@Nonnull/@Nullable` annotations
- [ ] New public APIs have `@since` tags in Javadoc

リンクされている PR 21319 と、参照されている前身の PR-18171 から始めてください。この tracking issue ではファイルやテストは指定されていません。引き受ける前に、Java 側の変更がすでに完了しているか、また Python クライアント側に残っている作業があるかを確認してください。

索引モデルが issue の本文から書いたものです。