[DDW-1203] Define a proxy for currency conversions

[michalrus]

This PR defines an OCI container which serves as a proxy for our currency conversions

Todos

• ask SRE to run it on our infra – https://input-output-rnd.slack.com/archives/C032DECBR6G/p1683650799513779
• switch the URL from http://localhost:8095 to the public one from SRE

Screenshots

n/a

Testing Checklist

• Slack QA thread
• Test all places where currency conversions are used

---

Review Checklist

Basics

• PR assigned to the PR author(s)
• input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
• If there are UI changes, Alexander Rukin assigned as an additional reviewer
• All visual regression testing has been reviewed (assign run Chromatic label to PR to trigger the run)
• PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
• PR link is added to a Jira ticket, ticket moved to In Review
• PR is updated to the most recent version of the target branch (and there are no conflicts)
• PR has a good description that summarizes all changes
• PR contains screenshots (in case of UI changes)
• CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
• There are no missing translations (running yarn manage:translations produces no changes)
• Text changes are proofread and approved (Jane Wild / Amy Reeve)
• Japanese text changes are proofread and approved (Junko Oda)
• Storybook works and no stories are broken (yarn storybook)
• In case of dependency changes yarn.lock file is updated

Code Quality

• Important parts of the code are properly commented and documented
• Code is properly typed with typescript types
• React components are split-up enough to avoid unnecessary re-renderings
• Any code that only works in main process is neatly separated from components

Testing

• New feature/change is covered by acceptance tests
• New feature/change is manually tested and approved by QA team
• All existing acceptance tests are still up-to-date
• New feature/change is covered by Daedalus Testing scenario
• All existing Daedalus Testing scenarios are still up-to-date

After Review

• Update Slack QA thread by marking it with a green checkmark

[marcin-mazurek]

@michalrus do we want to use dev-preprod instance for production, or is it for testing purposes, to give @gytis-ivaskevicius an OK from our side? Although I appreciate the network assignment is artificial in this case, I think for actual production builds we shouldn't use anything that has dev in its name, since it might not be stable enough

[michalrus]

@marcin-mazurek yes, I agree! I thought we might change the domain after QA approves this, which will allow Gytis to set up a production environment. Maybe we should then run just a quick QA test with the updated domain ?

[marcin-mazurek]

@michalrus perfect, that was my understanding, I'll just add DO NOT MERGE label to avoid confusion.

[miorsufianiohk]

LGTM. Great work @michalrus 👍