Customers sometimes run into scenarios where they are unable to scan important files that they would expect to scan using our tool due to file sizing constraints. For example a 400MB JAR file would be expected to be scannable if one wasn't aware of the size constraints of scanner today.{}

FUNCTIONAL REQUIREMENTS

1. Add the ability to modify the Scanner ConfigMap value maxExtractableFileSizeMB to the Helm Chart and Operator so that users can increase this upper limit when they are using helm or the Operator as a primary means of management and installation. 

UX/UI

Name the field scanner.maxextractablefilesize and rather add a note that this must be in megabytes.

DOCUMENTATION REQUIREMENTS

Document the new field for the helm chart

DEMO REQUIREMENTS

N/A

TESTING GUIDANCE

Ensure that a JAR file can be scanned within the defined constraint in the configmap.

Open Questions

1. Is there a better solution such as editing the configmap directly for this or would it be better to do it in the Operator/Chart.

See discussion in https://srox.slack.com/archives/C01Q93MMCNT/p1643649696368679