tarolog and tros should belong to picodata

The problem is that tros and tarolog create circular dependency on upgrading tarantool module in picodata. tros and tarolog depend from tarantool-module, picodata depends from tarantool module, and picodata-plugin depends from tarolog and tros. So previously when we wanted to do a major bump of tarantool module we did the following:

1. major release of tarantool module
2. update tros tarolog and several other crates like tarantool-test to depend from recent tarantool-module
3. finally bump tarantool module in picodata

This is hugely troublesome and creates a lot of friction especially during releases. Also note that at least 3 tarantool-module latest releases all have been major ones.

The plan is to move tros and tarolog to picodata repo, ideally tarantool-module should absorb them.