Pre-build manifest to optimize hash calculations for cache busting

[coderabbitai]

This issue tracks a future optimization to pre-build a manifest file for cache busting, avoiding hash calculations on each pod startup.

Context:
The current cache busting implementation in PR #192 calculates file hashes on-demand when generating cache-busted URLs. While this works, it means every pod instance needs to calculate hashes for all static assets during startup or first access.

Proposed Enhancement:
Implement a manifest-based approach where:

• Asset hashes are pre-calculated during build time
• A manifest file maps original paths to their cache-busted equivalents
• Pods can load this manifest instead of computing hashes at runtime
• Improves startup time and reduces compute overhead

Benefits:

• Faster pod startup times
• Reduced CPU usage across multiple pod instances
• Consistent hashes across all instances without recalculation

Related:

• Implementation PR: feat: Adds support for cache busting #192
• Discussion: feat: Adds support for cache busting #192 (comment)

Priority:
Future optimization - current implementation is functional, this would improve performance at scale.

Requested by: @nielsenko