We currently have the ZAP Advanced scans disabled in CI because they run too long. We would like to get them working again. One proposal is:

• Run them in the CI if files related to ZAP-Advanced have changed (but not otherwise), and
• run them in a nightly build to test them against (merged) changes to operator, SDK, etc.

Other options can also be viable and are left at the discretion of the person implementing this.