Enable AVM inside BulkExecuter based on given config

[AlexandraRoatis]

Description

Ensures the AVM is used only when enabled.

Type of change

Insert x into the following checkboxes to confirm (eg. [x]):

• Bug fix.
• New feature.
• Enhancement.
• Unit test.
• Breaking change (a fix or feature that causes existing functionality to not work as expected).
• Requires documentation update.

Testing

Please describe the tests you used to validate this pull request. Provide any relevant details for test configurations as well as any instructions to reproduce these results.

• existing tests + sync on mastery

Verification

Insert x into the following checkboxes to confirm (eg. [x]):

• I have self-reviewed my own code and conformed to the style guidelines of this project.
• New and existing tests pass locally with my changes.
• I have added tests for my fix or feature.
• I have made appropriate changes to the corresponding documentation.
• My code generates no new warnings.
• Any dependent changes have been made.

[AionJayT]

LGTM

[aionick]

Not a big fan of this means of passing the value. It puts the burden of knowing how to use an internal detail on the caller, when the bulk executor can grab this answer itself internally without any assistance from the config. A detail like this will eventually leak into unit tests, for example.

[AlexandraRoatis]

I understand your point of view, but the caller should be in charge of directing behavior here. If every class queries the config when it chooses there is more potential for errors (especially when you consider that the config is malleable and something like the GUI may choose to edit it) than if one entity directs overall behavior. The tests should be written to consider both AVM enabled and disabled.