[CI] Dockerize (add to docker-compose) all Travis CI Linux tasks

[asfimport]

Parent issue for migrating Travis CI tasks to Docker and decoupling from Travis-specific environment variables and image state

Reporter: Wes McKinney / @wesm
Assignee: Krisztian Szucs / @kszucs

Related issues:

• [Java] Dockerize Java builds in Travis CI, run multiple JDKs in single entry (is a parent of)
• [R] Dockerize R Travis CI tests so they can be run anywhere via docker-compose (is a parent of)
• [CI] Dockerize "lint" Travis CI job (is a parent of)
• [C++] Dockerize C++ with clang 7 Travis CI unit test logic (is a parent of)
• [Rust] Dockerize (add to docker-compose) Rust Travis CI build (is a parent of)
• [C++] Dockerize C++ CI job with conda-forge toolchain, code coverage from Travis CI (is a parent of)
• [Python] Dockerize (add to docker-compose) Python Travis CI job (is a parent of)
• [CI] Dockerize (add to docker-compose) Integration tests Travis CI entry (is a parent of)
• [JS] Dockerize NodeJS Travis CI entry (is a parent of)
• [GLib][Ruby] Dockerize (add to docker-compose) current GLib + Ruby Travis CI entry (is a parent of)
• [Go] Dockerize Travis CI Go build (is a parent of)
• [CI] Refactor docker-compose setup and use it with GitHub Actions (is superceded by)

_{Note: This issue was originally created as ARROW-5801. Please see the migration documentation for further details.}

[asfimport]

Wes McKinney / @wesm:
The proper state for this issue is probably "Resolved' not "Closed"