fix: allow AND and OR inside alb query conditions

[Inqnuam]

Closes: #11880

More details here

Should we add a depreciation warning for the previous schema as it is ambiguous and not well documented ?

query:
  bar: true

This lets us think that query value is a boolean like in REST API (http) schema, which isn't!

And we can't guess without deploying and testing what is the behaviour of this declaration:

query:
  foo: true
  bar: true
  baz: false

Actually if one of these keys (foo, bar, baz) is present in query string then the request will be accepted.

PS: as documented by AWS, query key isn't required and can be omitted