support for rebuilding software or removing paths before ingestion

[boegel]

We should be able to instruct the bot to remove existing installations, so they get rebuilt.

The removal also needs to be done during deploy.

Can be communicated by adding json info in the PR description?

{"rebuilds": ["example/1.2.3", "example/2.4.5"]}

[update 2024-02-06]
Metadata that comes with the tarball should specify which actions should be taken as part of the ingest.

• paths to remove
• list of tarballs to ingest => single staging PR!
• example

"payload": {
    "remove": ["path1", "path2", ...],
    "add": [{
    "filename": "eessi-2023.06-software-linux-x86_64-intel-skylake_avx512-1704485930.tar.gz",
    "size": "601491765",
    "ctime": "Fri Jan  5 20:20:16 UTC 2024",
    "sha256sum": "ded54f4555bf0411f8dc61e2a9b8f78b321533b978231543ed9d00a61c20ae2f",
    "url": "https://software.eessi.io-2023.06.s3.amazonaws.com/2023.06/software/linux/x86_64/intel/skylake_avx512/1704485930/eessi-2023.06-software-linux-x86_64-intel-skylake_avx512-1704485930.tar.gz"
  }},

• ingest script will need to be updated accordingly as well
• should work based on metadata files in S3 bucket (not tarballs)
  cfr. approach in NESSI (see upload tarball and metadata file to different directories in S3 bucket #241)