fix(jest-circus): reverse order of afterEach, afterAll hooks

[justjake]

Summary

fixes #12678

Currently, jest-circus runs afterAll and afterEach hooks in declaration order. However, both the docs and jasmine2 show afterAll and afterEach hooks running in reverse declaration order. This makes intuitive sense when using beforeEach to set up resources, and afterEach to dispose of resources:

let resource1: Resource
let resource2: Resource
beforeEach(() => { resource1 = new BaseResource() })
afterEach(() => { resource1.dispose() })

beforeEach(() => { resource2 = new ResourceConsumer(resource1) })
afterEach(() => { resource2.dispose() }) // May use resource1 after resource1 is disposed

This PR reverses the order of afterAll and afterEach hooks before they are executed.

Test plan

I added a snapshot test to jest-circus that emits output in the order shown in the documentation: https://jestjs.io/docs/setup-teardown#scoping

[github-actions]

This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[satanTime]

Up

[github-actions]

This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This PR was closed because it has been stalled for 30 days with no activity. Please open a new PR if the issue is still relevant, linking to this one.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.