fix: add cache-buster for provided images

[AlexAndBear]

Description

Related Issue

Update

• Fixes <issue_link>

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Types of changes

• Bugfix
• Enhancement (a change that doesn't break existing code or deployments)
• Breaking change (a modification that affects current functionality)
• Technical debt (addressing code that needs refactoring or improvements)
• Tests (adding or improving tests)
• Documentation (updates or additions to documentation)
• Maintenance (like dependency updates or tooling adjustments)

[AlexAndBear]

Why this approach?

This solution uses query parameters (?v=VERSION) for cache busting, which is the most pragmatic choice for our use case:

✅ Advantages:

• Simple and maintainable: No complex build configuration changes needed
• Standard practice: Used by major CDNs (Google Fonts, jQuery, Bootstrap)
• No breaking changes: URLs stay the same, just a parameter added
• Works immediately: No manifest system or lookup tables required
• Package-based versioning: Only invalidates cache on actual releases, not every dev build

🤔 Why not hash-based filenames?

We considered using Vite's built-in asset hashing (icon-abc123.svg), but:

1. vite-plugin-static-copy doesn't support hashing - files are copied as-is
2. Would require custom tooling: Need to build a manifest mapping icon-name.svg → icon-name-abc123.svg
3. Breaking change: All icon URLs would change, requiring lookup system
4. Complex for 1000+ icons: Dynamic access pattern (icons/${name}.svg) would need refactoring
5. Vite's public/ directory also doesn't hash - same problem, different location

📊 Comparison:

Approach	Complexity	Breaking Change	Works Now
Query parameters (this PR)	Low	No	✅
Hash in filenames	High	Yes	❌
Import as modules	High	Yes	❌

The query parameter approach solves the user-reported issue (stale icons after updates) with minimal changes and maximum compatibility.

[fschade]

clever!

[AlexAndBear]

clever!

🤷‍♀️