This change adds the server start timeout to the PRESERVE_ENVVARS
environment variable to deliver it to 'packpack' docker containers
while running packaging workflows.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

It looks like the step for storing the artifact with logs after workflow
failures was missed. Now it is added.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

This change adds facility to store artifacts with logs after workflow
failures to FreeBSD workflows. The ChristopherHX/github-act-runner known
limitation

    You won't be able to run steps after a failure without using
    continue-on-error: true

is not relevant anymore [1]. So we can add steps with storing artifacts.

[1] https://github.com/ChristopherHX/github-act-runner/tree/58ae37abc6c2244d91822b8ba536aa0a8b829632#known-limitations

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

This change fixes hardcoded artifact paths by using ${{ env.VARDIR }}
expression.

At this moment VARDIR=/tmp/tnt, so affected workflows are:
- debug_aarch64.yml
- memtx_allocator_based_on_malloc.yml
- osx_11_aarch64.yml
- osx_11_aarch64_debug.yml

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

This change updates the 'test_odroid_arm64_no_deps' make target in the
.travis.mk file with the following construction instead of `make test`:

    make LuaJIT-test
    cd test && ./test-run.py --vardir ${VARDIR} --force $(TEST_RUN_EXTRA_PARAMS)

This is needed for consistency with other targets and saving artifacts
with failure logs to ${VARDIR}.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

This change tries to fix the following sporadic test error:

    [007] not ok 4	http_client.sock_family:"AF_INET".test_cancel_and_errinj
    [007] #   ...arantool/tarantool/test/app-luatest/http_client_test.lua:221: Timeout check - status
    [007] #   expected: 408, actual: 200

Fixes tarantool/tarantool-qa#154

NO_DOC=testing
NO_TEST=testing
NO_CHANGELOG=testing

zlib.net is unavailable, so we have to download zlib distributions
from a backup storage on VKCS S3.

NO_DOC=testing
NO_TEST=testing
NO_CHANGELOG=testing

We need it for audit log.

NO_DOC=refactoring
NO_TEST=refactoring
NO_CHANGELOG=refactoring

The newly released 0.26.0 emits a warning on the `_box` variable.
From luacheck v.0.26.0 release notes:

"Function arguments that start with a single underscore
get an "unused hint". Leaving them unused doesn't result
in a warning. Using them, on the other hand, is a
new warning (№ 214)."

NO_DOC=testing
NO_TEST=testing
NO_CHANGELOG=testing

Reverting changes from 3cad9398,
originally introduced in 0b46154f

NO_DOC=testing
NO_TEST=testing
NO_CHANGELOG=testing

@TarantoolBot document
Title: Document constraints and foreign keys

See details here:
https://docs.google.com/document/d/1EtqfFSIMi6fDqj2y-9WgpunkHsszU65p6LfNly5E9Ag/

NO_TEST=no code changes

Implement complext foreign keys addition to field foreign keys.
They are quite similar to field foreign keys, the difference is:
* The are set in space options instead of format field definition.
* Several fields may be specified in relation.
* By design field foreign keys are more optimal.

One can set up foreign keys in space options:
box.schema.space.create(.. {.., foreign_key=<foreign_key>})
where foreign_key can be of one of the following forms:
 foreign_key={space=..,field=..}
 foreign_key={<name1>={space=..,field=..}, ..}
where field must be a table with local -> foreing fields mapping:
 field={local_field1=foreign_field1, ..}

NO_DOC=see later commits
NO_CHANGELOG=see later commits

Foreign key is a special type of constraint that makes a relation
between spaces. When declared in some space, each tuple in that
space refers to some tuple in another, foreign space. Reference is
defined in foreign key definition as a correspondence of field of
that spaces, local and remote.

Foreign key preserves that reference between tuples and consists
of two checks:
1. When a tuple is added to space with foreign space constraint,
it must be checked that there is a corresponding tuple in foreign
space, with the same values in fields according to foreign key
definitiion.
2. When a tuple is deleted from space that is a foreign space for
some other space, it must be checked that no tuple references the
deleted one.

This commit introduces field foreign keys that link spaces by
just one field. They are declared in tuple format in one of the
following forms:
 space:format{..,{name=.., foreign_key=<fkey>},..}
 space:format{..,{name=.., foreign_key={<name>=<fkey>}},..}
Where fkey has a form of a table:
 {space=<foreign space id/name>, field=<foreign field id/name>}

NO_DOC=see later commits
NO_CHANGELOG=see later commits

There are cases when we need to be sure that a space by given
id or name is not deleted; and if it is replaced (in space cache),
there's need to track pointer to new space. Like ib constraints:
they must hold a pointer to struct space while it's very hard to
determine whether there'a constraint that points to given space.

Implement space pin/unpin for this purpose. You can pin a space to
declare that the space is require to exist. To have to unpin it
when the space is not needed anymore.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

I'm going to extend space cache API so it should be separated.
One function went to space.h/c.
No logical changes.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

The previous commit adds tuple constraint lua functions that check
format of entire tuple. The problem was that in those functions
tuple could be accessed only by field indexes.

Add an ability to use field names too.

NO_DOC=see later commits
NO_CHANGELOG=see later commits

Implement whole tuple constraints in addition to field constraints.
They are quite similar to field constraints, the difference is:
 * The are set in space options instead of format field definition.
 * Entire tuple is passed to check function.
 * By design field constraints are a bit more optimal.

One can set up constraint in space options, with one or several
functions that must be present in _func space:
box.schema.space.create(.. {.. constraint='func1'})
box.schema.space.create(.. {.. constraint={name1='func1'})
box.schema.space.create(.. {.. constraint={name1='f1', name2='f2'})

NO_DOC=see later commits
NO_CHANGELOG=see later commits

tuple_format_new has lots of arguments, all of them necessary
indeed. But a small analysss showed that almost always there are
only two kinds of usage of that function: with lots of zeros as
arguments and lots of values taken from space_def.

Make two versions of tuple_format_new:
simple_tuple_format_new, with all those zeros omitted, and
space_tuple_format_new, that takes space_def as an argument.

NO_DOC=refactoring
NO_CHANGELOG=refactoring

Introduce field constraints - limitaions for particular fields.
Each constraint must refer to a function in _func space. For the
first step we expect lua functions with body there.

Field constraint checks are very close to field type checks, so
it's natural to implement them in tuple formats. On the other hand
tuple formats belong to tuple library, that does not include
functions (func.h/c etc), so constraints are split into two parts:
- a part in tuple library that implements arbitrary constraints
 with pointers to functions that actually check constraints.
- a part in box library which uses the part above, sets particular
 check functions and handles alter etc.

There are two not-so-obvious problems that are solved here:
 - Functions in _func space must be preserved while used by such
 constraints. Func pinning is used for this purpose.
 - During initial recovery constraits are created before _func
 space recovery, so we have to pospone constraint initialization.

One can set up constraint for any field in tuple format with one
or several functions that must be present in _func space:
space:format{name='a', constraint='func1'}
space:format{name='a', constraint={name1='func1'}}
space:format{name='a', constraint={name1='func1', name2='func2'}}

So constraint(s) can be set by one function name or by lua table
with function name values. Each consraints has a name that can be
specified directly (with string key in table) or imlicitly set to
the name of function.

The check function receives two arguments: the checking value and
the name of the constraint. Also the name of the failed constraint
is present in raised exception.

The only way to pass the constraint is to return true from its
function. All other values and exception are treated as failure
(exeptions are also logged).

NO_DOC=see later commits
NO_CHANGELOG=see later commits

Now C port allows to add a tuple or raw msgpack to it.

Add another function that encodes and appends given string.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

gpr_alloc is a small library that is designed for simplification
of allocation of several objects in one memory block. It could be
anything, but special attention is given to string objects, that
are arrays of chars.

Typical usage consist of two phases: gathering total needed size
of memory block and creation of objects in given block.

NO_DOC=refactoring
NO_CHANGELOG=refactoring

There's several important stages of recovery of database: loading
from snapshot, then loading from WAL(s) and then normal operation.

Introduce a global recovery state that shows this stage.

Note that there's already a recovery state in memtx engine which is
very close but still different to the new introduced state. That
state in memtx is a private property of memtx that internally shows
initialization status of memtx spaces and indexes. Memtx can set the
value for convenience' sake, for example it can jump directly to
MEMTX_OK before snapshot loading in case of force recovert.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

opt_def is an option parser from msgpack by given scheme.
The scheme consists of set of predefined types that the parser
can handle (something like int, enum, str). The problen is that
those predefined types must be generic, but there are cases when
a specific unusual must be parsed.

This patch introduces OPT_CUSTOM type that uses arbitrary function
callback and can be used for any non-generic option value.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

There are cases when we need to be sure that a function is not
deleted and/or removed from func cache. For example constraints:
they must hold a pointer to struct func while it's very hard to
determine whether there'a constraint that points to given func.

Implement func pin/unpin for this purpose. You can pin a func to
declare that the func must not be deleted. To have to unpin it
when the func is not needed anymore.

NO_DOC=refactoring
NO_CHANGELOG=refactoring

- Use uint32_t for string length. Actually internally it cannot
take more that INT_MAX length, so uin32_t is enough. This change
makes the hash table a bit more compact.
- Rename mh_strnptr_find_inp -> mh_strnptr_find_str. I beleive it
makes it more understandable.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

I'm going to extend func cache API so it should be separated.
A couple of comments added.
No logical changes.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

Fill port with a corrupted data in debug (TRASH it) in order to
detect double port destruction early.

Add a comment for func_call function that describes what states
of ports are expected before and after func_call.

Fix port usage in lua using ffi - allocate a full port structure
instead of a (bit smaller) structure port_c. That makes any port
structure to have fixed determined size which in turn makes safe
to cast and use different port types.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

There must be a normal code flow: if you want to initialize some
structure you should set members you want to and set with defaults
the rest members. Such a code flow would be durable when some new
members are added to the struct.

Make field_def structure to comply those rules.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

It seems that is was simply forgotten.

NO_DOC=refactoring
NO_CHANGELOG=refactoring
NO_TEST=refactoring

Some non-important fixes that are not related to any issue.

NO_DOC=refactoring
NO_CHANGELOG=refactoring

fselect is designed to make selects results in console better
readable for human eyes. The usage is expected to be rare and
by developers only so there's no performance requirements.

Now the API of fselect is:
s:fselect(<key>, <select+fselect option map>, <fselect option map>)

But sometimes there are cases when only some columns are needed
for analysis, while all other columns consume space on screen.

So make an option in fselect that allows to choose which columns
to output (like some other databases allows).

Add an option 'columns' in fselect options along with other its
options with list of columns (by number or name). Allow lua tables
and comma-separated-strings for that.

If options argument in fselect is string, interpret is as columns
options.

NO_DOC=There's no doc about fselect yet, I'll append these change
to the existing doc ticket
NO_CHANGELOG=minor changes in minor feature

We should link box_test_utils to tuple perf test to
prevent this error.

Follow up #2717

NO_CHANGELOG=build fix
NO_DOC=build fix
NO_TEST=build fix

Added 290 sec. timeout for starting tarantool server.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

Bump test-run to new version with the following improvements:
- Add timeout for starting tarantool server (tarantool/test-run#302)
- Kill hanging processes of not started servers (tarantool/test-run#332)
- Rerun all failed tests, not only marked as fragile
  (tarantool/test-run#329)

NO_DOC=testing
NO_TEST=testing
NO_CHANGELOG=testing

Running of luacheck against test-run submodule is redundant.
Add dedicated bypass to .luacheckrc.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

Investigation of GNU libunwind problems on the aarch64-linux-gnu
platform drive us to the conclusion that libunwind-1.2.1 provided by
major distribution packages is broken. Not to mention that its test
suite fails with SEGFAULTs.

Last but not least, some distributions, e.g. CentOS 8 (see #4611) do
not provide a libunwind package.

Hence, bundle libunwind: bundling is enabled by default on all
platforms, except for macOS — a system package can be used if its
version is greater or equal than 1.3.0 (minimal version that does not
seem to be broken on aarch64-linux-gnu).

* Add new submodule: bump it to current master.
* Refactor libunwind package search logic out of compiler.cmake.
* Add CMake script for building bundled libunwind.
* Add CMake script for extracting version of libunwind.
* Re-enable backtrace for all RHEL distributions by default.
* Remove libunwind from static build.

Needed for #4002
Closes #4611

NO_DOC=build system
NO_TEST=build system

It looks like we just missed the fuzzing.yml workflow when worked on
adding this feature to our CI process in #6446.

Follows up tarantool/tarantool-qa#100

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

It looks like this trigger was added beforehand for some purposes
but never used. So there is no sense to keep it in our workflows.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

We have recently moved all development from local branches to forks and
disabled running workflows in forks. So there is no sense to keep logic
for running full testing in forks if a branch has the 'full-ci' suffix.

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci

We have recently moved all development from local branches to forks.
Most workflows cannot be run in forks because many of them need access
to private runners and/or secrets.

Workflows in forks can be disabled manually, but it's hard to remember
and it needs an extra action from a developer. Instead, we can detect
the repo in workflows and run them if the repo is tarantool/tarantool.

Closes #6913

NO_DOC=ci
NO_CHANGELOG=ci
NO_TEST=ci