MicronautTest could support NOT starting @Scheduled methods

[sdedic]

Feature description

During a @MicronautTest run, a controlled fixture of certain beans and mocks is created to test a specific bean, but the all classpath-reachable beans are defined, and all reachable @Scheduled methods are potentially executed, even though their bean (e.g.) @Singleton is not referenced from the test's beans closure.

This complicates fixture creation (e.g. missing dependencies, ....) , sometimes the bean must be scheduled in other way than @Scheduled annotation because of this.

Micronaut Test infrastructure could support disabling or postponing start of the scheduled code until after e.g. some micronaut test API call that releases the schedulers.

[sdedic]

For reference, see https://github.com/sdedic/micronaut-dbbugs2/tree/scheduled-beans-unreferenced branch scheduled-beans-unreferenced; there's a simple ScheduledBeansTest which does not reference / inject anything, but allows ScheduledBean Singleton to be enabled.