Fix asset loading for web

[phixMe]

Problem

Since we updated the webpack version our asset loading broke and this has resulted in us having to make some undesirable changes to load images from remote instead of local sources.

Solution

This fixes the webpack configuration and allows for files to be imported in a more modern capacity that enforces the assets actually exist.

Note: All database schema changes require discussion. Please link the issue for context.

Checklist

• You've signed-off your work
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
• You've versioned your .sql database schema migration according to Flyway's naming convention (if relevant)
• You've included a header in any source code files (if relevant)

[codecov]

Codecov Report

Merging #2323 (467e806) into main (bc27201) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #2323   +/-   ##
=========================================
  Coverage     76.72%   76.72%           
  Complexity     1177     1177           
=========================================
  Files           222      222           
  Lines          5354     5354           
  Branches        429      429           
=========================================
  Hits           4108     4108           
  Misses          768      768           
  Partials        478      478           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[phixMe]

Potentially add other asset types here in the future, .jpg .png for example.

[wslulciuc]

@phixMe, looks like you'll have to sign your commits, but otherwise this looks great!