Lock in "js" feature for uuid on wasm builds

[mxgrey]

An update to uuid now requires the js feature to be explicitly enabled when targeting wasm. The latest version of bevy has fixed this upstream, but our main is still depending on bevy 0.12, which so far has not been updated.

There are two ways we can fix this for ourselves:

1. Lock the version of uuid down to a known-good version, such as 1.4.1
2. Lock the version of uuid up to 1.13.1 and then explicitly enable the js feature

I've opted for (2) so that we don't lose the benefit of whatever updates come into the uuid library over time.

I've already tested that these changes work for the web build of rmf_site_editor, although we will probably need to do a cargo update on the lockfile of the site editor.