TMP: test the node_modules named volume approach

[KevinMind]

Relates to: https://mozilla-hub.atlassian.net/browse/ADDSRV-720

Description

TMP: testing out using a docker managed volume for node_modules directory to resolve the docker/host permissions issue.

Context

This should allow us to simplify our npm setup, using the default directory, while avoiding the host/container permissions issue by makin the node_modules exist in a docker managed volume.

Testing

TBD: just testing out now.

[KevinMind]

Note: This build is

1. not failing when a test fails, this is a problem, needs to be fixed.
2. the reason it is failing is because the files static/js/zamboni/stats-all.js is created during the docker build, but does not exist in the host when we run the container. Docker does not merge bind mounts from the host with the container file system, but replaces the path so if the file doesn't exist in the host file system when we run, it is effectively "removed" in the container.

This needs to be addressed, there are a few potential solutions:

• make sure built files are placed in an ignored directory on the container. like "node_modules" is in the docker ignore, so it is safe for the container to write files there, the host will not overwrite them. We could put our build assets in a ./dist folder or something and then ignore that directory from the host.
• we could make sure to re-build assets when running the contianer (inefficient, boo)
• we could have a smarter mount volume when running, only mounting what and when we need to in CI.