Optimize method and hybrid starts by removing unecessary affected test classes computation

[mmk-1]

• I've removed the parts that computed affectedTestClasses for optimization.
• nonAffectedMethods variable was not used anyways in the code so I removed that too
• As an outcome of removing affectedTestClasses computations, methodToTestClasses mapping wasn't needed in HybridMojo.java either.

[owolabileg]

@mmk-1 let's think carefully about these changes, before merging them.

I've removed the parts that computed affectedTestClasses for optimization.

IIUC, these affectedTestClasses maps method-level changes to the class level. Is that right? If so, we'd need something like that for experiments. So, instead of deleting, why not make it an option that the user can enable or disable?

nonAffectedMethods variable was not used anyways in the code so I removed that too

It seems that you would need this variable when you later implement all the variants (e.g., to avoid instrumenting nonAffected methods. Does that make sense?

As an outcome of removing affectedTestClasses computations, methodToTestClasses mapping wasn't needed in HybridMojo.java either.

Please see my comment above: should we make it an option instead of outright deleting it?

[mmk-1]

Yes you're right. I'll make changes to introduce a parameter to turn this feature on/off

[mmk-1]

@owolabileg I have added new parameters based on your reviews to make Affected Test Class computation optional. Please review. Thanks!

[owolabileg]

This all looks good to me, and I think you can merge.