Fix optimistic query invalidation and avoid invalidating the same query twice

[slax57]

Problem

#11013 introduced a fix for optimistic query invalidation, but it was reverted in #11016 because it resulted in duplicate dataProvider calls in some scenarios.

Solution

The initial implementation of #11013 introduced invalidating queries using the provided query keys list, but also kept invalidating queries from the snapshot. This could result in calling queryClient.invalidateQueries() twice on overlapping query keys.

For instance:

[
    "posts",
    "getList"
]

and

[
    "posts",
    "getList",
    {
        "pagination": {
            "page": 1,
            "perPage": 10
        },
        "sort": {
            "field": "published_at",
            "order": "DESC"
        },
        "filter": {}
    }
]

This is what caused the duplicate call to getList.

The solution is to only keep the provided query keys list, because the snapshot is created from this provided list, so the query keys from the snapshot are a subset of the provided query keys set.

How To Test

• Open the simple example
• Edit a post and save
• Make sure there is only 1 getList call

Additional Checks

• The PR targets master for a bugfix or a documentation fix, or next for a feature
• The PR includes unit tests (if not possible, describe why)
• The PR includes one or several stories (if not possible, describe why)
• The documentation is up to date

Also, please make sure to read the contributing guidelines.