Situation
Currently when a scan type is defined in PDS server configuration, but the executor configuration on SecHub side uses another scan Type for the product, the PDS will execute scan anyway.
Example
iac PDS solution (Kics) does provide iacScan, but can be currently called with codesScan.
Look into PDSWorkspacePreparationContextFactory in method prepareContextForSupportedDataTypes. Here we see that only when no scanType is set an exception appears
Wanted
A wrong configured executor call shall trigger PDS, but PDS shall not execute with wrong scantype