Tarantool has been integrated to OSS-Fuzz infrastructure, and
implemented fuzzers are passed now [1]. Patch adds a new workflow that
will execute fuzzers on each push to a master branch using OSS-Fuzz
infrastructure [2]. To reduce a load on testing machines job triggers on
changes in directory with Tarantool's source code, fuzzers source code,
corpus files and GH Actions workflow file for fuzzing.

OSS-Fuzz provides web interface with fuzzing statistics, found errors
and other useful information. Access to OSS-Fuzz web interface is
available for persons whose email addresses specified in project.yml,
committed to oss-fuzz repository [4]. Bugs found in OSS-Fuzz reported to
bugtracker [5].

Using fuzzing testing documented in Tarantool's wiki [6].

1. https://github.com/google/oss-fuzz/pull/4723
2. https://google.github.io/oss-fuzz/getting-started/continuous-integration/#integrating-into-your-repository
3. https://google.github.io/oss-fuzz/further-reading/clusterfuzz/
4. https://github.com/google/oss-fuzz
5. https://bugs.chromium.org/p/oss-fuzz/issues/list
6. https://github.com/tarantool/tarantool/wiki/Fuzzing

Follows up #1809

Found that in commits:

  c53c650e ("github-ci: port perf jobs from gitlab-ci")
  5c68884a ("github-ci: add jepsen* test jobs")

was mistakenly missed "or" check "if:" condition, fixed.

Follows up #5663
Follows up tarantool/tarantool-qa#79

Added Github local Action 'perf' to be used for perf docker images
preparations and benchmarks runs. Ported jobs from gitlab-ci:

  perf_cbench
  perf_linkbench_ssd
  perf_nosqlbench_hash
  perf_nosqlbench_tree
  perf_sysbench
  perf_tpcc
  perf_tpch
  perf_ycsb_hash
  perf_ycsb_tree

Closes #5663

Pip and jq installation may fail if the host is real, in this way it
should be manually pre-installed.

Moved from gitlab-ci to github-ci 'jepsen*' jobs for
testing Tarantool with long Jepsen tests:

  jepsen-single-* jobs run by cron each 3 hours
  jepsen-cluster-* jobs run manualy or with API backend request.

Closes tarantool/tarantool-qa#79

Ported from gitlab-ci FreeBSD 12 build as a standalone Github
Actions workflow. Used sh4/sh8 local hosts as self-runners with
label 'freebsd-sh'. These hosts based on CentOS 7 with FreeBSD
12.1 installed in VBox VM. It was tried to use runners from
Github Actions which based on OSX, but failed to build FreeBSD 12
there, created additional issue to investigate the issue [1].

Closes #5754

[1]: https://github.com/tarantool/tarantool-qa/issues/81

The processing of the message to be sent via Telegram is separated for
OSX and other platforms for two reasons:
 * there is no need to wrap newline symbol with a single quote marks
 * backslashes used in the message haven't to be escaped

The link to the failed job log is not saved in other GitHub Actions
links. At the same time this link can be obtained via the following
command using GitHub API:

 $ curl -s https://api.github.com/repos/tarantool/tarantool/actions/runs/${{  github.run_id }}/jobs | jq -r '.jobs[0].html_url'

The obtained link for the particular run has the following format:
https://github.com/tarantool/tarantool/runs/<id>, where 'id' is the
number of the job.

This link is added to the Telegram message for the failed job which ID
is set as suggested in GitHub docs[1].

[1]: https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#example-6

Moved from gitlab-ci to github-ci 'osx_10_15_lto' job for
building/testing Tarantool on OSX with LTO.

Moved from gitlab-ci to github-ci 'static_build*' jobs for
building/testing Tarantool on Linux and OSX. Added targets
in .travis.mk file for static build on OSX on Github hosts.

Closes #5661

Moved from gitlab-ci to github-ci 'out-of-source' job for
building/testing Tarantool in standalone build path while
source path is not writable.

Closes #5660

Moved from gitlab-ci to github-ci 'default_gcc_centos_7' job for
building/testing Tarantool on default GCC installed in CentOS 7.
Removed not used after movement templates from gitlab-ci config.

Artifacts paths for pack/deploy/osx based jobs corrected.

After commit:

  a598f3f5 ('test: update test-run (pass timeouts via env)')

The following variables added to github actions with testing:

  REPLICATION_SYNC_TIMEOUT
  TEST_TIMEOUT
  NO_OUTPUT_TIMEOUT

and cumulative variable to pass environment to pack/deploy jobs:

  PRESERVE_ENVVARS=REPLICATION_SYNC_TIMEOUT,TEST_TIMEOUT,NO_OUTPUT_TIMEOUT

These variables added within newly added local action:

  .github/actions/environment

Used Telegram public channel to send notifications for failed Github
Actions workflows. Created new Github Action based on Python:

  .github/actions/send-telegram-notify/action.yml

with the ability to send messages in MarkdownV2 format [1]. To make
able to run standalone Github Action used its 'composite' type [2].
Also added ability to logout Github environment variables in this
action.

[1] - https://core.telegram.org/bots/api#markdownv2-style
[2] - https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action

Added condition in gitlab-ci and github actions to skip testings
when branch names ends with '-notest'.

CMake 3.1 or newer is essential for implementing LuaJIT self-sufficient
testing environment (see more info in the next patch). Unfortunately,
not all distributions provide the required CMake from the repositories.
Here is the actual list of default packages providing CMake for the
distributions that support Tarantool:
| Distro             | CMake version | Repo                |
|--------------------+---------------+---------------------|
| CentOS 6           | 2.8.12        | base                |
| CentOS 7           | 2.8.12        | base                |
| CentOS 8           | 3.11.4        | appstream           |
| Debian Jessie      | 3.0.2         | jessie/main         |
| Debian Stretch     | 3.7.2         | stretch/main        |
| Debian Buster      | 3.13.4        | buster/main         |
| Fedora 28          | 3.14.4        | updates             |
| Fedora 29          | 3.14.5        | updates             |
| Fedora 30          | 3.17.2        | updates             |
| Fedora 31          | 3.17.4        | updates             |
| Fedora 32          | 3.17.4        | updates             |
| FreeBSD 12         | 3.15.5        | default             |
| OSX 14             | 3.19.3        | brew                |
| OSX 15             | 3.19.3        | brew                |
| Ubuntu 14.04       | 2.8.12        | trusty/main         |
| Ubuntu 16.04       | 3.5.1         | xenial-updates/main |
| Ubuntu 18.04       | 3.10.2        | bionic-updates/main |
| Ubuntu 20.04       | 3.16.3        | focal/main          |
| openSUSE Leap 15.1 | 3.10.2        | Main                |
| openSUSE Leap 15.2 | 3.17.0        | Main                |

As one can see, there are no required packages provided by default for
the following distributions: CentOS 6, CentOS 7, Debian Jessie and
Ubuntu 14.04. There are alternative packages (i.e. cmake3) providing a
newer CMake than the default one for the old packages:
| Distro             | CMake3 version  | Repo                    |
|--------------------+-----------------+-------------------------|
| CentOS 6           | 3.6.1           | epel*                   |
| CentOS 7           | 3.17.5          | epel*                   |
| Ubuntu 14.04       | 3.5.1           | trusty-updates/universe |

(*) Unfortunately, I failed to find the way to make rpmbuild install
    and enable EPEL repository prior to the build step. However,
    cmake3 requirement obligues user to enable EPEL by himself,
    otherwise this dependency is left unmet. If there are any issues
    with building an RPM on CentOS 7 please proceed to the docs[1].

So the last problem is Debian Jessie: the required CMake toolchain is
provided neither via the default repository nor via the auxiliary one
(e.g. kinda updates repository like it's done for Ubuntu 14.04). Anyway,
Debian Jessie long term support has reached its EOL[2], so we can freely
drop this distribution from our regular build testing.

[1]: https://www.tarantool.io/en/doc/latest/dev_guide/building_from_source/
[2]: https://www.debian.org/News/2020/20200709



Relates to #4862

Reviewed-by: Alexander V. Tikhonov <avtikhon@tarantool.org>
Signed-off-by: Igor Munkin <imun@tarantool.org>

Added jobs for testing and deploying Fedora 33 packages.

Added Fedora 33 at update_repo tool to make able to save packages
in S3 buckets.

Closes #5502

Removed CentOS 6 from packages build jobs as already removed at:

  8b08a3ba ("gitlab-ci: remove CentOS 6")

Ported source and packages deploy jobs from gitlab-ci to github-ci.

Closes #5662

Found that artifacts uses storage space which is limited to 0,5 GiB.
To avoid of lack of the space there decided to decrease the retention
days option for artifacts from default 90 days to 21 days (3 weeks).

GH allows to create custom templates for different kind of issues.
So two separate types of templates added: for feature requests and
for bug reports.

GH also allows to redirect users from a new issue page to external
resources. So requests with commercial support redirected to Tarantool
website and questions redirected to GH Discussions.

Old bug report template has been removed.

Closes #5642

Now we have a PID 1 zombie reaping problem, when zombie processes
launched in Docker aren't collected by init, how it would be done if we
launch it on a real host.

It is fixed by adding --init option, when a container is created or
started.

Co-authored-by: Artem Starshov <artemreyt@tarantool.org>

Follows up #4983

Found that in previous commit to debian_11.yml file were made mistakes
in git refs/heads paths:

  e0a33ffe ("github-ci: build packages for debian-bullseye")

This patch fixes it.

Follows up #5638

Added package workflow to github actions. Set deployment of the
packages for the master branch and tags.

Closes #5638

Initially decided to use external module:

  fkirc/skip-duplicate-actions

but after some additional investigation [1], decided to use simple check

  github.event.pull_request.head.repo.full_name != github.repository

instead of this module. This solution was found in github.com/h2o/h2o
repository [2].

Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org>

[1] - https://github.com/tarantool/tarantool/pull/5638#discussion_r549248841
[2] - https://github.com/h2o/h2o/commit/1c79d79e8b7686145975bc1cb04201e78b875924

Due to current testing schema uses separate pipelines per each testing
job then workflow names should be the same as jobs to make it more
visible on github actions results page [1].

[1] - https://github.com/tarantool/tarantool/actions

Found that jobs on push and pull_request filters run duplicating each
other [1][2]. To avoid of it found additional module [3]. Used entire
jobs skip on duplicated jobs either previously run jobs in queue that
were already updated [4].

[1] - https://github.community/t/duplicate-checks-on-push-and-pull-request-simultaneous-event/18012
[2] - https://github.community/t/how-to-trigger-an-action-on-push-or-pull-request-but-not-both/16662
[3] - https://github.com/fkirc/skip-duplicate-actions#concurrent_skipping
[4] - https://github.com/fkirc/skip-duplicate-actions#option-1-skip-entire-jobs

Added standalone job with coverity check as described at [1]. This
job uploads results to coverity.com host to 'tarantool' project when
COVERITY_TOKEN environment is enabled. Main coverity functionality
added at .travis.mk make file as standalone targets:

  'test_coverity_debian_no_deps' - used in github-ci actions
  'coverity_debian' - additional target with needed tools check

This job configured by cron scheduler on each Saturday 04:00 am.

Closes #5600

[1] - https://scan.coverity.com/download?tab=cxx

Moved coverage saving to coveralls.io repository from travis-ci to
github-ci. Completely removed travis-ci from commit criteria.

Part of #5294

Implemented github-ci action workflow OSX jobs on commits:
 - OSX 10.15
 - OSX 11.0

Part of #5294

Implemented github-ci action workflow on commits.
Added group of CI jobs:

  1) on Debian 9 ("Stretch"):
    - luacheck
    - release
    - debug_coverage
    - release_clang
    - release_lto

  2) on Debian 10 ("Buster")
    - release_lto_clang11
    - release_asan_clang11

Part of #5294