Also, some cleanup

Co-authored-by: NLove Kristofer Leifland <love.leifland@neotechnology.com>

Setting is deprecated and was removed in a523c195. However, setting must still exist with `@Deprecated` annotation for proper API documentation, and in order to show up in `SHOW SETTINGS`.

Fixes a race condition causing incorrect reporting of counts to the
page cache tracer when closing a transaction, after running an embedded
query with the parallel runtime and using the Core API on returned entities
within a result transformer.

The problem was that the ValueMapper used in ResultSubscriber was exposing
the internal transaction directly to returned entities, which could lead
to uses of ambient cursors updating non-threadsafe counts while execution
contexts were merging their reports back to the transaction on query close.

This is solved by providing the subscriber with an ExecutionContextValueMapper
based on the execution context of the resources used for query intialization.
These resources now have to be closed from the query calling thread after
merging of worker execution contexts is completed.

.. to distinguish the case where the user has provided different type constraints for the same (label/type, property)-pair.

Collapse nested JSON objects in the query logger when `db.logs.query.annotation_data_as_json_enabled` setting is true

Log4j's filter and `fluentd` do not handle nested JSON objects by default. This PR changes the behavior to collapse them with dots, e.g.

```
{
    "annotationData": {
        "type": "system",
        "source": "foo"
    }
}
```

to

```
{
    "annotationData.type": "system",
    "annotationData.source": "foo"
}
```

This will allow for smoother integration with existing tools without the need to resort to error-prone regex parsing of JSON.

Fixes: #13090

For the 0-th repetition, the node patterns outside the QPP are bound to the same node and the predicates inside the QPP are not enforced.

Uses the ServerPoliciesPlugin applied with the current RoutingContext when determining if execution should be local or remote. If remote, then we use the plugin again to form the routing table for the driver (meaning that routing context is now part of the key for cached driver instances).

Return a rich result containing the internal bolt addresses and server ids.

Co-authored-by: NLasse Heemann <lasse.heemann@neo4j.com>

This way,there is no need to implement the runtime for the notIsTyped AST.

Graph selection was handled only by Query router/Fabric layer and USE clauses were stripped from queries
there before queries were sent to Cypher stack.
In order to simplify Query router, queries are sent to Cypher stack unmodified. Allowing USE clause in layers
bellow Query router means that some checks must be performed there mainly because of queries submitted
through Core API.
Co-authored-by: NLinneaAndersson <linneamaria10@gmail.com>

Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>

- Includes both test construction and production code construction
Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>

- For some test scenarios the expression rewriting wasn't happening before this change.
- Also now ensures that rewriting _always_ happens after parsing an expression.
Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>

Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>

New kernel version 5.9 connected to the type constraints
Exposes type constraints on Core API

Introduces property type constraints to restrict the type of node and/or relationship properties. Can be created with commands like:
CREATE CONSTRAINT nodePropertyStringType FOR (n:Label) REQUIRE n.prop IS :: STRING or CREATE CONSTRAINT relPropertyBooleanType FOR ()-[r:REL_TYPE]-() REQUIRE r.prop IS :: BOOLEAN

The degree store would not seek in "previous changes" correctly, which could result in incorrect reported degrees during checkpoint which in turn could result in count store corruption

The precedence for IS NULL and IS NOT NULL were broken by mistake while adding the GQL IS keyword.

This commit disallows the labels NOT, NULL and TYPED for label expressions with the IS keyword and unescaped labels.
Co-authored-by: NNadja Müller <nadja.muller@neotechnology.com>