Problem

We do not upload frontend source maps or releases to Sentry. This prevents the Sentry UI from being able to identify where in the code an exception actually happened or tell us when an issue is related to a new release/if a new release is unhealthy.

Description

We should try to use the Nuxt plugin's publishRelease settings to enable this: https://sentry.nuxtjs.org/configuration/options/#publishrelease

Note that git-related settings will not work because we build the application inside a docker container without the git repository available.

We could change that by building the application on the CI box instead of inside a container and then copying the release in (this might actually simplify things for us, with the frontend, considering the complexities we have with build contexts for it) but that's work for a separate issue, if we do it at all (it has its own trade-offs).

Finally, it isn't clear to me whether doing this will automatically make source map uploads work. The Nuxt plugin's documentation is not clear on this. We can try to get the releases working first and then check to see if the source maps are available. If they are, great! If not, then we need to figure out why. They're available on the actual website, publicly, but Sentry recommends uploading and associating them with a specific release because it can them more reliably associate the line of code for a release for a given event.