paritydb panics when used for light client

[dvc94ch]

So we stopped using our custom sled db setup and noticed that it doesn't work.

The problem comes from optimizations being enabled for column::STATE which has col_id 1, which aren't valid when using the light client that has KEY_LOOKUP as col_id 1. As a workaround the optimizations can be disabled.

[bkchr]

CC @arkpar