Having dynamic build as a default was dictated by certification and now
when we merged certification patches back to master it started to cause
friction. So this patch makes static build the default and introduces
dynamic_build cargo feature instead of static_build one.

1. Add a new option picodata run --shredding to enable shredding upon xlog_remove_file_impl.
2. For test purposes additionally use the inject_errors feature to keep files after shred operation
and allow the test code to look inside and make sure that content was really shredded.

It was rebased recently on top of the same 2.11.2-picodata

Note: this changes return values from all .proc_* stored procedures,
making them more usable, but completely breaking the compatibility with
older versions.

Closes #500

Use single step after system specific requirements. Do not use system
packages on ubuntu.

This way helps us to avoid installing native dependencies needed for
dynamically linked binary.

Yaroslav Dynnikov authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

It's unused since 44a0fc61

- update sbroad submodule to commit with
support of except for global tables
- add integration tests for except with
global tbls

- update sbroad submodule to commit
supporting union all with global tbls
- add integration tests

New feature `static_build` is added to Cargo.toml. By default dynamic
build is being used. build.rs is changed to respect it.

Use `cargo build --features static_build` to build static binary.

Previous attempt directly modified static-build cmake files which
is less convenient and doesnt allow us to support both build types
at the same time

Replaces https://git.picodata.io/picodata/tarantool/-/merge_requests/143 and https://git.picodata.io/picodata/picodata/picodata/-/merge_requests/817

- remove logical clock from raft entry context, (term, index) is used
  for synchronization instead
- this allows us to remove the Notify/Notifier boilerplate
- NodeImpl::notifications -> NodeImpl::read_state_wakers
- this and the recently refactored proc_join finally allows us to remove
  OpResult
- ContextCoercion & CoercionError are also removed for the sake of
  simplification

Is needed because ipv6 is not available on CI but localhost is resolved
to both v4 and v6 addresses

By adding a comment here in ce9ddc26
I made the whole command to be ignored because for gitlab > means single
command that is split across lines, so by starting it with # on the
first line I made the whole command a comment.

See https://docs.gitlab.com/ee/ci/yaml/script.html#split-long-commands
for details.