Ron Buckton

This now includes the `await using` declaration and `AsyncDisposableStack`, per prior consensus (incl. the March 2023 plenary).

Note to implementers: There is a typo in `GetDisposeMethod` that will be addressed by https://github.com/tc39/proposal-explicit-resource-management/pull/217. The typo was introduced as part of a normative change that reached consensus in July...

This is also missing the consensus change to use `await using` as the syntactic head for the asynchronous form of the `using` declaration. That will be up shortly.

25f1bc4a4c19a0cc202d25567573d098e239b911 applies changes from the following PRs which previously achieved consensus in [March 2023](https://github.com/tc39/notes/blob/970d84b7d0f9c455757870a3892ea78e7bee2cfd/meetings/2023-03/mar-21.md#conclusion-8) and [July 2023](https://github.com/tc39/notes/blob/970d84b7d0f9c455757870a3892ea78e7bee2cfd/meetings/2023-07/july-11.md#conclusion-6): - tc39/proposal-explicit-resource-management#180 - tc39/proposal-explicit-resource-management#178 - tc39/proposal-explicit-resource-management#175 - tc39/proposal-explicit-resource-management#171 - tc39/proposal-explicit-resource-management#167 - tc39/proposal-explicit-resource-management#154 -...

I can rebase but I'm not a huge fan of rewriting git history since that will break PRs against this PR.

Rebased (twice, to make GitHub happy). Hopefully that fixes the PR in the diff review website.

@bakkot, @syg, @michaelficarra: I am hoping to ask for Stage 4 at the May plenary, but this PR still requires reviews from the editors.

> @rbuckton Noted, we'll get to it ASAP. If we don't get to it before the meeting you're welcome to ask for stage 4 pending editor review, and then assuming...

@typescript-bot test top400 @typescript-bot user test this

@typescript-bot test top10.00