Fix Dockerfile for Angular 13 updates

[tdonohue]

References

Related to discussion on Slack where @kshepherd noticed our dspace-angular Docker container was only listening on localhost. This caused the UI to be unresponsive unless you accessed it from within the running Docker container (via wget or similar)

Description

During the Angular 13 upgrade (#1567), the yarn serve command (which is used to run the app in dev mode) was updated to use ng serve (Angular) instead of node. This had the unfortunate side effect of limiting the dspace-angular docker container to listening only on localhost instead of on 0.0.0.0 (default for node) because ng serve defaults to localhost, see https://angular.io/cli/serve

This small PR fixes our Dockerfile to specify --host 0.0.0.0 to ensure it listens to all IP addresses, and not only to localhost.

Instructions for Reviewers

Using this PR, try the following:

• Rebuild your local dspace-angular Docker container: docker-compose -p d7 -f docker/docker-compose.yml build
• Spin it up & verify the UI now works: docker-compose -p d7 -f docker/docker-compose.yml up -d

[tdonohue]

NOTE: I've just realized with additional testing that Dev Mode isn't fully working in Angular 13.. see #1614 . So, while this PR "works", it causes Docker to use config.prod.yml instead of config.dev.yml.

So, this PR is a partial fix, and it appears to be dependent on first fixing #1614

[kshepherd]

@tdonohue just a note, in my local fix i instead updated package.json serve profile like this:
"serve": "ng serve -c development --host 0.0.0.0", (just adding the --host flag)
And it seemed to work, and I think development mode seems to work OK - I can log in, when I copy over new files the source is recompiled, etc.
It also doesn't require the docker image to be rebuilt and works for both dev and production. However, it would affect servers running normally, not just docker services and could be a security or configuration problem.

Happy to just +1 and merge this if the Dockerfile is a better approach -- since the package.json fix would also affect non-Docker instances, it could be a security issue. But thought I'd note it here.

(what if we added a new serve:dev or something, that could include the --host 0.0.0.0 line in the ng serve command?)

[kshepherd]

+1, tested and working. Will merge this now as it is high priority and allows yarn/ng to bind properly, though as per the last comment this might only be a partial fix or could be substituted for a different fix in future