Implement noUninitializedPrivateFieldAccess assumption

[nicolo-ribaudo]

• copy test cases from 2023-05

• update 2023-11 test options

• copy applyDecs2305 to applyDecs2311

• allow 2023-11 decorator version

• feat: support per-field intitializers

• update test fixtures

OVERWRITE=1 yarn jest decorators -t "2023 11"

• update generated helpers

• update other class tests

• expand field-initializers-after-methods case

• Add failing private flavour test

• update pipeline operator tests

• Don't run Babel 8 test with 2023-05 decorator

• add release todo item<!--
  Before making a PR, please read our contributing guidelines
  https://github.com/babel/babel/blob/main/CONTRIBUTING.md

Please note that the Babel Team requires two approvals before merging most PRs.

For issue references: Add a comma-separated list of a closing word followed by the ticket number fixed by the PR. (it should be underlined in the preview if done correctly)

If you are making a change that should have a docs update: submit another PR to https://github.com/babel/website
-->

Q	A
Fixed Issues?	Fixes #1, Fixes #2
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?
License	MIT

Following up to the recent changes, this PR makes it possible to also avoid the extra object for static private fields. The drawback is that at runtime an uninitialized static private field on the correct receiver looks just like if it was already initialized but to undefined.

[nicolo-ribaudo]

Without the assumption, this would be

class A {
  static dynamicCheck() {
    babelHelpers.assertClassBrand(this, A, _x)._;
    _x._ = babelHelpers.assertClassBrand(this, A, 2);
    [babelHelpers.assertClassBrand(this, A, _x)._] = [];
  }
  static noCheck() {
    _x._;
    _x._ = 2;
    [_x._] = [];
  }
}
var _x = {
  _: 2
};

The "assigned in destructuring" case gets worse, but it's a very rare operation to do compared to normal usage of private fields.