They are faster and they provide a easier-to-use standalone voms-proxy-fake.
Moreover the Java clients have some issues at the moment and its equivalent
of voms-proxy-fake doesn't work well.

Do not restore a working directory at the end of the function, since
there was no previous directory change.

Added voms-clients-java

gitlab-ci and readme need to be updated

Specify the correct location of the nginx-httpg_no_delegation.patch file in the script for installing openresty-voms in the devcontainer

Remove user ownership and add executable permission to build-install-openresty-voms script.

Use both provide-deps.sh files in devcontainer:
 * provide-CI-deps.sh install the deps for CI
 * provide-dev-deps.sh install the remaining deps for the devcontainer

Before this update, provide-CI-deps.sh was a subset of provide-dev-deps.sh

To distinguish the differet provide-deps.sh in the same folder, one for the CI container, one for the devel container

Use name conventions in .devcontainer

From git224 to git236

This script is used during the CI.

It is moved from .devocontainer to docker folder, probably this is not the correct place.

The build-install-openresty-voms.sh script is copied in /usr/local/bin instead ~/bin.

Deleted the addition of ~/bin from PATH env variable.

DEV_USER -> USERNAME
DEV_USER_UID -> USER_UID
DEV_GID -> USER_GID

See the best practise:
https://github.com/microsoft/vscode-dev-containers