translate steps partially

[RamyAlshurafa]

Issues this PR relates to

#225

Note

when the user goes to the landing page, the page requests all the steps, so we translate all the steps at once, which makes the translation API respond with too many requests errors.
this fix is to change the get steps logic, only to get the title and the description for the steps, so we translate these two fields, and when the user views a single step we translate the whole step. this makes fewer data to be translated at the same time

=======

NOTE: REMEMBER NOT TO REVIEW UNLESS ALL ACCEPTANCE CRITERIA HAS BEEN TICKED OFF

---

Any info the reviewer needs to know to test

e.g. Add env vars, run npm install

---

Any info the team needs to consider before merged into development

e.g. Will a database need to be rebuilt (and is this ok if existing data), add env vars

---

Quick Pull Request Checklist

Please make sure you ensure the following has been done before marking your PR as awaiting-review.

• Branch is up to date with develop
• Project runs
• You can download and install locally, and run the project locally
• All existing and new features run without bugs
• Checked that features/design works across all agreed browsers + devices
• The new work has been checked with Axe accessibility checker and doesn't throw significant errors
• Linter is used
• Code is consistent with agreed team style
• Naming of files is consistent with project
• Tests all pass
• No console logs

[cemalokten]

@RamyAlshurafa The same issues seem to be happening as before, inconsistent gaps in the translations:

GET /api/steps?lng=fi