Run event loop after job application

[Sushisource]

What was changed

Run the event loop after applying all jobs, rather than after each "batch" of jobs.

Why?

Align with TS & Core's intended method of job application

Checklist

1. Closes [Feature Request] Consider aligning activation job application with TS changes #606

2. How was this tested:
   Existing & new tests

3. Any docs updates needed?

[Sushisource]

If it weren't for this bit we would've ended up with net-less code here. A bit too bad, but, I think still nicer than grouping things into batches.

[cretz]

Hrmm, I think another test may look like this:

• Create workflow that has a signal handler that updates some counter and an activity in the background that, when done, updates that same counter. And have the primary workflow method return the counter when it is > 2 (i.e. after wait condition for that).
• Start the workflow, and while the activity is running, kill the workflow worker
• While the workflow worker is not running, send two signals and complete the activity
• Start the workflow worker again and confirm result and confirm that all three of those items (the two signals and the activity completion) came in the same workflow task/activation.

I think with older code, the counter will only reach 2 before workflow returns (i.e. the two signals), but this newer code may return 3 (because it completed the activity before it processed wait condition). I have not tested this though.