fix: disable all scanners in emailsender central comp test

[johannes94]

Description

https://github.com/stackrox/stackrox/pull/17932/files
In stackrox/stackrox the emailsender tests are failing because of disk space and resource issues. It makes sense to disable scanner since the test is not using scanner related features. This will reduce disk space and resource requirements of the test and hopefully make it pass.

Checklist (Definition of Done)

• Unit and integration tests added
• Added test description under Test manual
• Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
• CI and all relevant tests are passing
• Add the ticket number to the PR title if available, i.e. ROX-12345: ...
• Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.
• Add secret to app-interface Vault or Secrets Manager if necessary
• RDS changes were e2e tested manually
• Check AWS limits are reasonable for changes provisioning new resources

Test manual

TODO: Add manual testing efforts

# To run tests locally run:
make db/teardown db/setup db/migrate
make ocm/setup
make verify lint binary test test/integration

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johannes94, kovayur

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [johannes94,kovayur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[johannes94]

/override ci/prow/e2e
/override ci/prow/images

[openshift-ci]

@johannes94: Overrode contexts on behalf of johannes94: ci/prow/e2e, ci/prow/images

Details

In response to this:

/override ci/prow/e2e
/override ci/prow/images

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.