fix: downgrade version of nest axios

[ludtkemorgan]

Issue Overview

This PR addresses Heroku deployment

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

With the most recent change of moving the purge calls from partners to the backend the deployment to the heroku failed. This is due to the way we have our backend setup. The yarn lock file is at the base level of the bloom repo and when deploying the backend all it knows about is what is in the backend/core directory. Because of this it does not find a yarn lock file and instead tries to do a fresh install using npm and the package.json file. For the most recent change it grabs the version of @nestjs/axios specified in package.json (2.0.0) and tries to download all of the dependencies. We don't have a high enough version of axios that we are requesting so the install fails.

This PR solves that problem by downgrading @nestjs/axios which is ok with the older version of axios. Long term we would like to solve this by upgrading both @nestjs/axios and axios but that will require changes to Partners and Public so this is a quick fix to solve it in the mean time.

How Can This Be Tested/Reviewed?

In order to test this I have deployed it to bloom backend main heroku (the one that normally deploys on merges to main). So you can test it here https://bloom.exygy.dev/ and https://partners.bloom.exygy.dev/. But it also doesn't hurt to pull it down locally to test

Checklist:

• My code follows the style guidelines of this project
• I have added QA notes to the issue with applicable URLs
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	534345d
🔍 Latest deploy log	https://app.netlify.com/sites/bloom-exygy-dev/deploys/6451606931d0e800078374c8
😎 Deploy Preview	https://deploy-preview-3419--bloom-exygy-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[YazeedLoonat]

LGTM

[ColinBuyck]

LGTM 🕹️