Fixed cvat_ui image build in case of OOM error

[azhavoro]

Fixed cvat_ui image build in case of OOM error.
There seems to be a bug in npm v6.x with signal handling on alpine based images only npm/cli#2103 and it won't be fixed for v6.x. This bug is not reproducible on debian buster based images and is not reproducible for npm v 7.x.
We are currently unable to switch to npm 7 easily, so I suggest using a buster based image as the first stage.

Motivation and context

resolve #2989

How has this been tested?

Previously, building the image with the following command docker build --memory 500M -f Dockerfile.ui . was successful, although npm run build was killed; for now it handles correctly

Checklist

• I submit my changes into the develop branch
• I have added description of my changes into CHANGELOG file
  - [ ] I have updated the documentation accordingly
  - [ ] I have added tests to cover my changes
• I have linked related issues (read github docs)
  - [ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
  cvat-core, cvat-data and cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.
• I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

[nmanovic]

@azhavoro , need to add a line to CHANGELOG.md