The script has mostly been copied from alphaplan_fwr.py, but with
different input data.

Adding a job to the CI-test environment for testing this.

This script has mostly been copied from alphaplan_fwr.py, but with
different input data (artifacts from the SoftwareStore deploy job) and
without actually importing the data to the Alphaplan database.

Adding a job to the CI-test environment for testing this.

Rename all stages to uppercase on this occasion, since we're adding
stages with names containing multiple words.

isort is a Python utility to sort imports alphabetically, and
automatically separated into sections and by type.

Instead of copying a packaged release from the SoftwareStore, download
artifacts from an actual build job.

This is a workaround to prevent customer releases being uploaded to our
public FTP area. It should be removed as soon as we support uploading to
different FTP target folders.

Customer specific manifest projects can now set the RELEASE_SUFFIX
variable, which then gets appended to the deployment folder names.

Otherwise it can be assumed that it might be correlated with
outputdir_local, which is not the case.

- Make output-dir an argument that can be passed multiple times instead
  of hard-coding two dirs with certain meanings.
- Remove LOCALDIR variable from package.env, because it is not used
  anywhere (only occurence was job class ".uploadsdkftp" which wasn't
  used anywhere either).

Improve readability of package_release.py and its submodule
generate_release_metadata.py.

- Add describing comments throughout the file.
- Remove duplicate code from functions. Simplify them, so that they do
  what their names say (and nothing more).
- Rename variables and function arguments to make their purpose clearer.
- Harmonize variable names with their corresponding command line arguments.
- Add pydoc for functions.
- Add type declarations to function arguments.
- Generate MD5 and metadata files in the source directories so that they
  can be copied along with the rest of the files.

Trying to query CI variables on a project which does not have the CI
feature enabled leads to an HTTP 403 (forbidden) error.
Check whether CI is enabled using the "jobs_enabled" flag.

The match to detect fngsystem still contained 'guf'. Changed to 'seco'.

BCS 746-001043

- Use "source" and "target" terminology in the script, just like in the
  GitLab CI variables.
- Spefify data types for function arguments.
- Rename function arguments to better reflect their data types.
- Move determination of integration branch into main function, so that
  the successfull status message can be more verbose.
- Remove parent_merge_request feature and checking for gitlab-ci
  integrations, because the check job does not run on gitlab-ci
  integration branches at all.

We don't need to explicitly trigger a build after merging changes in
gitlab-ci. A master pipeline on the target projects runs automatically.