This patch finally brings desired testing for static build packages.

How it works:

In a few words, we have two workflow files: calling and callable. The
callable workflow (static_build_pack_test_deploy.yml) is parametrized
and contains all the logic with the building, testing, and deploying
packages. It takes just two inputs: package platform and JSON matrix
for testing. The calling workflow (packaging.yml) just runs callable
one with specific parameters and contains all the logic related to
triggering by events and concurrency.

The static_build_pack_test_deploy.yml workflow consists of three jobs:
`build`, `test`, and `deploy`. Artifacts between jobs are passed via
the `upload-artifact` and `download-artifact` actions. The `test` job
is a matrix one and verifies packages on provided Linux distros passed
through input. After the testing is done, the `deploy` job is intended
to upload packages to repositories on a tag push, which means release
or pre-release.

Note, for starting Docker containers to test packages we use PackPack
images because they have almost all requirements to run tests.

Follows up #8771
Follows up #8840
Follows up #8866

Closes tarantool/tarantool-qa#322

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci