feat: put aggregate_state into assigns of the pipeline

[fahchen]

Assign aggregate_state, so that we can write middlewares to do more things about the aggregate_state in the after_dispatch stage.

[jvantuyl]

This isn't really necessary. If someone wants the :aggregate_state along with other information, they can ask for an :execution_result and pull it out of there.

[fahchen]

This isn't really necessary. If someone wants the :aggregate_state along with other information, they can ask for an :execution_result and pull it out of there.

@jvantuyl In fact, you cannot get the aggregate_state at after_dispatch, you mean you can get it after the entire dispatch is finished, right?

[jvantuyl]

Oh, I see. I was thinking you meant "after dispatch" semantically. Not the after_dispatch phase of the middleware. Nevermind, I see what you're getting at now.