Starting two content releases in the same second causes the pipeline to mix up the configuration #32
Description
Starting a release via startFullContentRelease creates an identifier based on the current second via the unix timestamp.
F.e. starting a second release for another workspace in the same second by another user can lead to a mixup in the pipeline.
In our case we ended up with a mixture of both configurations for each pipeline run and both succeeded but had the wrong result.
Also only one of the releases shows up in the ContentStore module.
Therefore the release id should be made more unique and checked for a duplicate.