jsonschema.exceptions.ValidationError: 'PORTS' is a required property

[underdarknl]

Describe the bug
When enabling a boefje without setting all its required settings (which is allowed due to the possible existence of env-vars), the boefje runner throws a jsonschema validationerror. this error however does not produce an error raw file accessible via the tasklist's job.

To Reproduce
Steps to reproduce the behavior:

1. Go to katalogus
2. Enable nmap-ports, do not fill out the number of ports
3. Scan an IP
4. See error, notice there's no raw files do the dowloaded.

Expected behavior
At least we should store the error/stacktrace and allow the user to see they need to conform the boefje's settings to the schema by adding settings or env-vars.

Screenshots

SettingsNotConformingToSchema: ('nmap-ports', "'PORTS' is a required property")
Traceback (most recent call last):
  File "/app/boefjes/boefjes/job_handler.py", line 85, in get_environment_settings
    validate(instance=new_env, schema=schema)
  File "/usr/local/lib/python3.11/site-packages/jsonschema/validators.py", line 1332, in validate
    raise error
jsonschema.exceptions.ValidationError: 'PORTS' is a required property

Failed validating 'required' in schema:
    {'title': 'Arguments',
     'type': 'object',
     'properties': {'PORTS': {'title': 'PORTS',
                              'maxLength': 2048,
                              'type': 'string',
                              'pattern': '^((6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})|(6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})-(6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4}))$|^((6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})|(6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})-(6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4}))(,((6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})|(6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})-(6553[0-5]|655[0-2]\\d|65[0-4]\\d{2}|6[0-4]\\d{3}|[1-5]\\d{4}|\\d{1,4})))+$',
                              'description': 'Specify the ports that need '
                                             'to be scanned (nmap format). '
                                             'Single ports are comma '
                                             'separated, port ranges can '
                                             'be specified using the dash '
                                             'symbol. For example: '
                                             '22,111,137,80-100 will scan '
                                             'ports 22, 111, 137 and the '
                                             'port range 80 up to 100.'}},
     'required': ['PORTS']}

On instance:
    {}

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/boefjes/boefjes/app.py", line 251, in _start_working
    handler.handle(p_item.data)
  File "/app/boefjes/boefjes/job_handler.py", line 135, in handle
    boefje_meta.environment = get_environment_settings(boefje_meta, plugin.boefje_schema)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/boefjes/boefjes/job_handler.py", line 87, in get_environment_settings
    raise SettingsNotConformingToSchema(boefje_meta.boefje.id, e.message) from e
boefjes.storage.interfaces.SettingsNotConformingToSchema: ('nmap-ports', "'PORTS' is a required property")

OpenKAT version
Main

[underdarknl]

@dekkers 's feedback boiled down to the broad catch all on both the boefje execution and the collection of resources. He feels catching all is too broad, and conflates possible errors in KAT (connectivity, config, others) with possible errors in the boefje.
Since we dont have another return channel for the errors in KAT, separate from the errors that might occur in the boefje, I feel our best bet currently is to use this boefje error channel to communicate in the broadest sense when something breaks when trying to run a boefje, regardless of where the error occurs.