Describe supported Tarantool versions with limitations

For those who interested to dig to a topic himself I recommend to start
with:
- search using of helper functions like utils.tarantool_supports_* in
source code base
- search conditions with `_TARANTOOL` in source codebase
- supported Tarantool versions by tuple-keydef module [1]
- source code for compatibility layer in CRUD
- "Select: support jsonpath indexes (#158)" (27d825f)

1. https://github.com/tarantool/tuple-keydef#compatibility

Author: ligurio

README.md

@@ -8,6 +8,29 @@ The `CRUD` module allows to perform CRUD operations on the cluster.
 It also provides the `crud-storage` role for
 [Tarantool Cartridge](https://github.com/tarantool/cartridge).
 
+# Supported Tarantool versions
+
+CRUD depends on Tarantool features like key_def and merger modules etc.
+Due to this some Tarantool versions has limited support in CRUD.
+
+- 1.10 (latest patch version)
+  - since 1.10.7-85-g840c13293, where tuple-keydef module became builtin.
+- 2.2 (latest patch version)
+  - since 2.2.2, where key_def has been introduced, see https://github.com/tarantool/tarantool/issues/3398
+- 2.3 (latest patch version)
+  - since 2.3.3 due to Tarantool's SEGFAULT, see https://github.com/tarantool/tarantool/issues/4954.
+  For Tarantool versions higher 2.x and lower 2.3.3 CRUD uses another implementation of select module,
+  see `crud/select/compat/select_old.lua`.
+- 2.5 (latest patch version)
+  - since 2.5.1-145-geea90d7ce, where tuple-keydef module became builtin.
+- 2.6 (latest patch version)
+  - since 2.6.0-188-g4a12985f1, where tuple-keydef module became builtin.
+  - since 2.6.3, where jsonpath indexes support for queries has been added
+- 2.7 (latest patch version)
+  - since 2.7.2, where jsonpath indexes support for queries has been added
+- 2.8 (latest patch version)
+  - since 2.8.1, where jsonpath indexes support for queries has been added
+
 ## API
 
 The CRUD operations should be called from router.