Fixes: Circle CI and Docker build failing due to unupdated version of node

[mahesh-naxa]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

Fixes the frontend tests failing issue on #6375 & develop branch.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[mahesh-naxa]

The tests seems to be working with the latest circleci image cimg/node:18.19.1.

However i am not sure why the image cimg/python:3.10.7-node was choosen for the deploy steps, I have replaced those with the cimg/node:18.19.1. If there wasn't a specific need the PR can be safely merged, without breaking the deployment steps.

Just to let you know i did test the install-ability these:

• libgeos-dev jq aws-cli
• @mapbox/cfn-config @mapbox/cloudfriend

tasking-manager/.circleci/config.yml

Line 187 in 3115315

- image: cimg/python:3.10.7-node

tasking-manager/.circleci/config.yml

Line 240 in 3115315

- image: cimg/python:3.10.7-node

(maybe just merging this and testing if the deployment works straight to our develop also could be wise @ramyaragupathy )
cc @eternaltyro @dakotabenjamin

[dakotabenjamin]

I think the reasoning was frontend uses node and backend uses python. If the node image contains a fixed version of python then it's all good to me IMO.