Add Bazel remote cache setup for CircleCI unix commands

[farost]

Usage and product changes

CircleCI has random fails because of some process races (when a setup process takes too much time to initialize) or network errors working with Bazel (Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/root/.cache/bazel/_bazel_root/37e9b89f8be6f62402523a372e67422a/server/jvm.out')).

To address the last problem, we connect CircleCI builds to our Bazel remote cache for each Bazel operation on Unix-based systems. This way, we won't send too many requests to the remote Bazel servers, using already existing build results from our cache when it's possible.

Implementation

We add a remote cache setup call before each Bazel command for Unix CircleCI builds.

[vaticle-bot]

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

---

Trivial Change

• [ ] This change is trivial and does not require a code or architecture review.

Code

• [ ] Packages, classes, and methods have a single domain of responsibility.
• [ ] Packages, classes, and methods are grouped into cohesive and consistent domain model.
• [ ] The code is canonical and the minimum required to achieve the goal.
• [ ] Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
• [ ] Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
• [ ] The code is algorithmically efficient and scalable for the whole application.

Architecture

• [ ] Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
• [ ] Any required build and release automations are updated and/or implemented.
• [ ] Any new components follows a consistent style with respect to the pre-existing codebase.
• [ ] The architecture intuitively reflects the application domain, and is easy to understand.
• [ ] The architecture has a well-defined hierarchy of encapsulated components.
• [ ] The architecture is extensible and scalable.

[farost]

This PR can cause some of the machines to have errors because of the too big amount of open files (it had already been tested before), so we don't go this way.