chore: test image generation

[dennyscode]

Ticket: https://lifi.atlassian.net/browse/LF-10000

Each route.tsx includes some notes with available params + example
As of now, I have created 5 endpoints to generate images: (1) selection of tokens -> (2) quotes -> (3) review -> (4) execution -> (5) success

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
jumper-exchange	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 18, 2024 3:28pm

[github-actions]

Playwright test results

 11 passed
 3 skipped

Details

 14 tests across 2 suites
 1 minute, 55 seconds
 edd0d5b

Skipped tests

chromium › e2e.spec.ts › Jumper full e2e flow › Should be able to navigate to profile and open first Mission
chromium › e2e.spec.ts › Jumper full e2e flow › Should be able to navigate to Supefest
chromium › e2e.spec.ts › Jumper full e2e flow › Should be able to open quests mission page and switch background color

[dennyscode]

@tcheee @oktapodia @admsk2

I need to pick your brain on the following:

1.) caching -> I am already trying but somehow feel like this is not the most we can get out of it (see image)

2.) url -> New images are placed inside public folder and needed during API calls -> How can I reference to it via a URL? (I need the origin of the url / baseUrl).
Good example: Feature-Branches do not have fixed URL´s. What´s best to make it work?