passing `convoState` in `nextAbility`

[howlowck]

Is your feature request related to a problem? Please describe. user should have access to convoState when deciding which ability to start next. However in order to have an accurate convoState, nextAbility has to be executed after the slot's onComplete is executed.

onComplete can be async, and the result of onComplete is done in the wolfMiddleware.

Describe the solution you'd like We should need to make another stage (say, kickoff) to be run after execute and before outtake. this proposed stage, is to find the nextAbility and kickoff the ability with the next query (or finish the ability if no slot is present)

Since the nextAbility could finish (when it has no slot), and requires another execute... and so on and so forth. this means the execute and kickoff is in a loop until there is no more nextAbility to finish.

[kevinleung23]

Started but deprioritized.. kslhacks/nextAbility branch.