Move reservine-button distribution to CDN

[LEFTEQ]

Summary

The reservine-button embed widget should be served from a CDN instead of the current distribution method. This would improve:

• Load performance — faster delivery from edge locations closer to end users
• Reliability — CDN redundancy vs single-origin serving
• Caching — proper cache headers and invalidation
• Scalability — offload bandwidth from the main infrastructure

Scope

• Set up CDN hosting for the built reservine-button web component bundle
• Update embed instructions / snippet URLs to point to CDN
• Ensure versioning strategy (e.g., v1/reservine-button.js or semver-based paths)
• Consider cache-busting strategy for updates

Labels

• enhancement
• infrastructure