gitlab-ci and readme need to be updated

Merge branch '30-bug-in-devcontainer-patch-file-not-found-in-openresty-voms-installation' into 'master'

Resolve "Bug in devcontainer: patch file not found in openresty-voms installation"

Closes #30

See merge request storm2/ngx_http_voms_module!22

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

Merge branch '28-using-an-embedded-variable-in-a-subrequest-causes-a-segmentation-fault' into 'master'

Resolve "Using an embedded variable in a subrequest causes a segmentation fault"

Closes #28

See merge request storm2/ngx_http_voms_module!20

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

In a subrequest, the http_connection field is NULL.

Issue #28

Resolve "Remove dependency from storm2/build project"

Closes #27

See merge request storm2/ngx_http_voms_module!19

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

All the file in assets used tu build the devcontainer are moved in library-script.

Modify the Dockerfile COPY directory

Change a reference to the storm2/build repository

The patch file used by the .devcontainer is needed only by  the build-install-ngx-voms.sh script. This script could use the patch file in the project home dir instead of the copy in the container.

Add an echo in the container specifing that the patch file must exists in the directory where the user runs the script.

Add  a check in the script: if the patch file isn't found, the script adivses the user and exits with an error.

The yum install commands were copy-&-paste from the 3  original images.
Now all the repo are installed first; then, they are followed by all the other packages merged together in a single yum install command.