Add: Support for specifying task type and complementary changes

[4D617274696E]

What

• Added the command line argument '--task-type' to specify the type of tasks to generate and add randomly generated reports to:
  • Can be 'container' or 'scan', default: 'container'.
  • Since reports cannot be imported into scan tasks, a workaround is used: a container task is created first, set to alterable, then reports are imported, then the container task is modified and a target, scanner and scan config are added. This automatically transforms the container task into a scan task.
  • Required objects for scan tasks, e.g. targets, are only generated when necessary.
• Changed logic for timestamp calculation from custom method and 'time' module to standard methods from 'datetime' module.
• Improved naming of randomly generated objects:
  • Added timestamps to names to make them uniquely identifiable and to prevent duplicated generations.
  • Added comments with extended information.
• Streamlined some text elements.
• Formatted with 'black'.

Why

OpenSight Asset requires scan tasks to import data from.

Checklist

• Tests

• Checked with pylint.
• Tested manually by generating 200 reports in several passes, and with a combination of command line arguments. Not every possible combination of command line arguments has been tested.
  • Test environment: gvm-cli 23.10.0 (API version 23.10.1) & GOS 22.04.15

[github-actions]

Conventional Commits Report

Type	Number
Bug Fixes	2
Changed	1
Added	1

🚀 Conventional commits found.

[bjoernricks]

Just one small change, please extract the

       (local_date_time + timedelta(seconds=-20))
        .astimezone()
        .replace(microsecond=0)
        .isoformat()

into a reusable function.
something like

def creation_time(delta: int = 0) -> str:
  return local_date_time + timedelta(seconds=delta))
      .astimezone()
      .replace(microsecond=0)
      .isoformat()
  )