Upgrade circleci base image used for docker build

[dmanjunath]

Description

Successor to #3157.

We are currently using an outdated CircleCI image to kick off docker builds (has no impact on the actual docker builds). This just updates to the latest image as recommended by CircleCI

Tests

Tested building images on CI and running then on staging nodes to verify they work.

How will this change be monitored? Are there sufficient logs?

The build success will be displayed in github with the CircleCI checks. The actual containers will be tested when deployed to staging.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
3509188	Generic High Entropy Secret	90976b5	.circleci/config.yml	View secret
3509188	Generic High Entropy Secret	90976b5	.circleci/config.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[dmanjunath]

fixed the issues @joaquincasares

[joaquincasares]

Looks good after this request!

[joaquincasares]

Lgtm!