Fix master branch issues

[elhimov]

This PR resolves all the problems found during investigation of the subject

Fixed 'no-ssl' build.

follow-up 331436c applying the approach introduced in 97f88ec

The mentioned approach implies using of lib/dial library rather than tls-dialer. The implementation of lib/dial depends on build type and either uses tls-dialer for 'ssl' build (tls-dialer in turn depends on OpenSSL c-library) or dummy implementation for 'no-ssl'.

Prior to this patch tls-dialer was used directly which means that tt-executable always required OpenSSL c-library (libssl.so).

Certain version of the SSL-library is resolved at build-time and depends on the build environment. So previously tt-executable always required libssl.so of the version that was installed on builder. Then if target system didn't have it tt executable failed to launch. This exact problem arose for example when one tries to install tarantool with the command:

$ tt install tarantool --use-docker

This command eventually launches tt in a docker container that is prepared internally and is based on Ubuntu 18.04 which have SSL of version 1 onboard. tt itself is usually built in modern environment with SSL of version 3 and thus its execution in docker failed.

Upgraded docker images that is used by tt to build tarantool.

tt performs tarantool in-docker compilation in the scope of commands

tt install tarantool --use-docker
tt pack tgz|deb|rpm --use-docker

Docker images that are used internally are based on Ubuntu 18.04, but starting from tarantool/tarantool@1fd4404 tarantool compilation no longer succeed in this system due to compilation issues. The problem has been fixed already (tarantool/tarantool#12170), but anyway there are a bunch of commits (including version 3.6.0 of tarantool) that can't be used with the commands mentioned above.

At the same time Ubuntu 18.04 is quite an old release that is no longer supported. So this patch bumps "base" of the tarantool-builder dockers to the next Ubuntu LTS which is 20.04 (its default c-compiler is not affected with the "problem" commits).

Test against predefined versions of tarantool in test_install_tarantool_in_docker

Prior to this patch integration test test_install_tarantool_in_docker doesn't specify tarantool version explicitly, so it was always checked against the latest one. Which means that it might fail due to some problem introduced in tarantool and thus it might break tt release cycle with non-tt problem.

To avoid such an unpredictable behavior this test is adjusted to check only against predefined tarantool versions (each of them is obtained from the corresponding test environment). Original test that checks against the latest tarantool version is to be moved to separate workflow that is not involved into release cycle and is performed periodically (by cron) to monitor consistency.

Fix installing tarantool by commit hash.

Prior to the correction installation-by-commit only worked with commits that are accessible from the current master's HEAD

I didn't forget about:

• Well-written commit messages (see documentation how to write a commit message)
• Don't forget about TarantoolBot in a commit message (see example)
• Tests (see documentation for a testing package)
• Changelog (see documentation for changelog format)

Related issues:

Closes #1220
Closes #1221
Closes #1222
Closes #1223
Related to tarantool/tarantool#12167

[patapenka-alexey]

LGTM!