Make user-data-permission-fix optional

[nerdinand]

Motivation and context

Deploying CVAT to OpenShift (see also #3992), we've run into problems with the user-data-permission-fix initContainer. OpenShift seems to be stricter in what you can do permission-wise. To mitigate this, we propose making the permission fix optional. Along with adding RUN /bin/chmod -R 777 ${HOME} to the Dockerfile, this works for us.

How has this been tested?

Helm chart tested manually

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

[nerdinand]

Maybe a better solution would be to add RUN /bin/chmod -R 777 ${HOME} to the Dockerfile in the first place, then this initContainer might become obsolete altogether. Thoughts?

[nmanovic]

@azhavoro , @ActiveChooN , could you please look?

[ActiveChooN]

Maybe a better solution would be to add RUN /bin/chmod -R 777 ${HOME} to the Dockerfile in the first place, then this initContainer might become obsolete altogether. Thoughts?

If this fix can be applied in the build stage it looks like a better solution.

[nmanovic]

@azhavoro , could you please review and share your opinion? Should we merge the PR?

[azhavoro]

LGTM

[nmanovic]

@nerdinand , thanks for the contribution.