Start from storm2/base, which just provides some users. Avoid
the large multi-language development environment of storm2/build.
In fact, it would not be too difficult to start directly from
the base CentOS image.

Split the setup in multiple phases:
- installation of packages (setup.sh)
- build/installation of openresty (build-install-openresty.sh)
- user environment configuration (user-setup.sh)

Files added in the home directory are given the proper ownership

The script adds lines to the .bashrc to:
- retrieve the build environment for openrety
- adding the bin directory to the PATH, where a script was placed
- provide a help message

This script now just builds openresty and saves some variables that will
be useful during development, namely the RESTY_CONFIG_OPTIONS and the
PATH where luajit has been installed.

Do not install any more needed packages, which are already installed
by a previous setup step run as root.

Upgrade Openresty version to 1.19.9.1.

Enable the `--with-compat` configuration option, so that other dynamic
modules can be integrated without recompiling everything.

Remove the `--with-dtrace-probes`, which is not supported any more.

Do not consider the possibility to use non-system versions of PCRE,
ZLIB and OpenSSL.

Do not touch the .bashrc, which is done by another script, so that this
script could possibly not be run.

This is part of a restructuring of the docker image setup, in particular
to separate actions done as root from actions done as a user

https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html

Updated boost version issue-9

See merge request !3

Update cmake to version 3.17.1

See merge request !2

See merge request !1