Load assets from relative path

[aceArt-GmbH]

Description

Deploying cinny on a sub path like /cinny/ breaks loading of some assets.
Use relative path to prevent 404s.

• rendering PDFs
• web app manifest
• web app icons
• web app start

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• 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

[github-actions]

Preview: https://1588--pr-cinny.netlify.app
⚠️ Exercise caution. Use test accounts. ⚠️

[aceArt-GmbH]

So it seems now the manifest is correctly prefixed if build.config.ts is changed.
And pdf.worker.min.js is also loaded correctly.
Only the contents inside the manifest are not changed by vite

[aceArt-GmbH]

So I just tested again. The paths in the manifest.json don't need further changing (from vite) as they are relative to the manifest itself.
So this should be fine now

[ajbura]

Thanks for the changes. LGTM now