QueryableInfoType.complete is not properly used for queryables with identical key expressions on the same face.

[DenisBiryukov91]

Describe the bug

QueryableInfoType.complete (in SessionContext and other structs) is not properly updated when declaring/undeclaring queryables if more than one queryable with the same key expression is declared for the same face. I.e on declaration of new queryable the .complete field is just overwritten to correspond to that of newly declared queryable, and when undeclaring queryable, this field is ignored if there are still remaining queryable with the same key expression.

To reproduce

The bug is easy to reproduce when using querier matching status/listener api introduced by #1591.

1. declare incomplete queryable on "some/keyexpr"
2. declare complete queryable on same keyexpr
3. declare complete querier on same keyexpr
4. undeclare complete queryable
5. matching status for querier will be true (despite the fact that the only remaining queryable is incomplete)

System info

any