[FEATURE] Provide option to disable the plugin

[FieteO]

• What are you trying to do?
  I want to enable the plugin only in the pipeline and not in local execution. I want to do this, because I want to develop without being required to locally have the credentials to the nexus that is used in the background.

• What feature or behavior is this required for?
  For instance in open source projects, you don't want the contributors to know credentials to your infra.

• How could we solve this issue? (Not knowing is okay!)
  Provide something like a

nexusIQScan {
    enabled = false
}
ossIndexAudit {
    enabled = false
}

setting.
I am sure I would be able to get the 'disabled' behaviour also by specifying a non-existing stage or by having some wildcard pattern for the modulesExcluded settings, but that would be much less convenient than having a dedicated property.
I hope I don't miss something here

cc @bhamail / @DarthHater / @guillermo-varela / @shaikhu

[github-actions]

Hi!

First of all, thank you for opening your first issue. Elementary, we appreciate all feedback that helps us continue improving this plugin.

As this is a community project we can't commit to official due dates for reviews and developing, but we're definitely committed to delivering services, integrations and plugins of top quality.

So please be patient, we will review your issue and get back to you as soon as we can!

Regards,
Sherlock Trunks 🐘

[guillermo-varela]

Hi @FieteO

Tasks in this plugin are not tied to others to force automatic execution as part of other lifecycle.

One would need to manually run ./gradlew nexusIQScan or ./gradlew ossIndexAudit for this plugin to actually scan, evaluate or audit dependencies.

If you're seeing unintentional executions of this plugin, could you please share console/log outputs?