Node starts with incorrect QueryEntity configuration

When QueryEntity.keyFields property is used to specify compound key fields, it is possible to set the field names in wrong register.
The node would start normally, but for SQL queries requesting key fields the resultset contains nulls in corresponding columns.
The query processor internally fails to tell the key field from value field in this case.
Note that for optimized marshaller, the keyFields aren't taken into account and queries return valid data.

I believe the node shall not start with such configuration at all.

See the attached test that reproduces the case.