* Add zap scanning for DocumentServer
* Set branch name as ref for manual trigger
* Use master as default zap action branch
* Move zap action to master branch
* Fix token variable name
* Small cosmetic fix
* Modify zap action trigger condition
Run zap scanner only when documentserver edition hit community and branch hit in `release/` or `hotfix/`
* Add the ability to rebuild images
Rebuilding images will be done manually (for now). The choice of the number of rebuilt releases is available (1 by default), the choice of repositories for pushing rebuilt images is available (4testing by default).
Principle of operation:
Through the api of the docker hub, we get the last launched tag that falls under the pattern x.x.x.1, after that the tag with the assembly of which the minor tag x.x will be sent will be calculated. Next, at one of the build steps, the number of the previous release will be received, for example x. x.x.4 which will mean that the current one will be x.x.x.5
* Add login to dockerhub
* Refactoring code
Set some variables for all rebuild-info job. Also set default values for repository and quantity variables
* Refactor: remove push trigger
* Refactoring code
* Refactor: Unlinking a version
* Submitting the latest tag for the latest release only
* Refactoring stable images release versioning
The new principle of stable docker images versioning: release numbering is now not by build number, but by serial number.
* Refactoring: fix non-example image pull tag
The key that is automatically generated weaken the security strength.
As noted in RFC7518 section 3.2 [0]:
```
A key of the same size as the hash output (for instance, 256 bits for
"HS256") or larger MUST be used with this algorithm. (This
requirement is based on Section 5.3.4 (Security Effect of the HMAC
Key) of NIST SP 800-117 [NIST.800-107], which states that the
effective security strength is the minimum of the security strength
of the key and two times the size of the internal hash value.)
```
Some JWT libraries are rejecting by default keys that are too small in
a attempt to prevent misusages so generating a key that does not respect
the minimal length can be problematic for OO integrations.
[0] https://www.rfc-editor.org/rfc/rfc7518.html#section-3.2
