Implement opentelemetry instrumentation in sbroad.
How to test:

docker run --name jaeger -d --rm -p6831:6831/udp -p6832:6832/udp \
-p16686:16686 -p14268:14268 jaegertracing/all-in-one:latest

Then run a stress test with sbroad. The results would be available
at http://localhost:16686/

Thanks to the updates in tarantool module we don't use tarantool
symbols to work with decimal. As a bonus we can remove our mocking
framework with dynamic linking of the decNumber library to cargo
test binary.

Previously, we created a static archives of the msgpuck and decNumber
libraries and made a statically linked them into the test executable.
After tarrantool module migrated to dlsym, we can no longer use static
linking.

As a result we build shared libraries for msgpuck and decNumber to
dynamic link them into the unit test binary.

picodata features enables Picodata Tarantool fork functionality
Schema enables functionality needed to operate spaces metadata

We want to get reproducible builds. Cargo.lock does exactly this.
On the start of the development we were following the rule that
"libraries does not include cargo.lock in git, binary does".
However we misinterpreted the role of Sbroad. It is built as a "cdylib"
so we should treat it as an executable and include cargo.lock