🎨 refactor: Prevent Font Asset Hashing in Vite Config

[danny-avila]

Summary

• Modified the assetFileNames function in the build.rollupOptions section of vite.config.ts.
• Implemented a conditional statement to check for font file extensions (woff, woff2, eot, ttf, otf).
• Set font assets to use the format 'assets/[name][extname]', preserving the original filename without a hash.
• Maintained the existing hash-based naming convention for all other asset types.

Change Type

• New feature (non-breaking change which adds functionality)

Testing

To test this change:

1. Run a build of the client application using npm run build or equivalent command.
2. Inspect the output directory, particularly the assets folder.
3. Verify that font files are named without a hash (e.g., fontname.woff2) while other assets still include a hash.
4. Test the application to ensure fonts are loading correctly and there are no regressions in asset loading.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• Local unit tests pass with my changes