Scheduling hook into ExecuteStateManagerImpl

[andresgalindo-stripe]

Context

Allow us to plug a hook that mutates the list of available task executors

Checklist

• ./gradlew build compiles code correctly
• Added new tests where applicable
• ./gradlew test passes all tests
• Extended README or added javadocs where applicable

[crioux-stripe]

Generally looks good, besides the (blocking) nit I left one more item to think about... What is the intention if the user wants multiple mutator hooks? Right now we could do a composite hook and that is probably fine.

[crioux-stripe]

nit: I generally prefer the overloaded constructor so that the tests / clients who do not use the change do not need to change in any way to ignore new functionality. Especially true since the Netflix injector will likely break without having an appropriate Bean.

[github-actions]

Test Results

622 tests  ±0   612 ✅ ±0   8m 2s ⏱️ +8s
142 suites ±0    10 💤 ±0 
142 files   ±0     0 ❌ ±0 

Results for commit 80865c8. ± Comparison against base commit d2f7ff7.

♻️ This comment has been updated with latest results.

[andresgalindo-stripe]

@crioux-stripe I've gone ahead and overloaded .props() to keep one that matches the signature of what was there before

w.r.t multiple hooks, yep, my thought that it was more flexible for the user if they implement a ChainedHook themselves and let them define how they want to cycle through hooks themselves (e.g. if one hook returns no instances do we just return all instances from the previous hook in stack in an attempt to schedule no matter what, or, do we really return nothing / throw an exception to stop this from being scheduled, etc)