As part of #15722, the jsii targets for experimental packages on the v2 branch
were changed to include an 'alpha' identifier so the package and module names
would more obviously reflect the stability of the packages.

However, since this change was made directly to the package.json files, this
means that all usages of these targets across the source were impacted,
including usages via ubergen. The impact of this is that the L1s published to
aws-cdk-lib were incorrectly published under this 'alpha' module instead of
their normal location. L1s should still go under the standard location, as they
are stable; only the experimental L2s should be impacted by the alpha
designator.

fixes #15845

…mation

As part of #15722, the decision was made to change the package.json files for
experimental packages to add 'alpha' identifiers. This ends up causing issues
for our ubergen-ed packages (i.e., aws-cdk-lib), which then try to include L1s
for these packages under the 'alpha' namespaces. Instead, switch (back) to
adding the alpha identifiers as part of the package transformation step.

Reverted the change to the pkglint rules, and re-ran `yarn pkglint` to update
the package.json files.

I also did some light refactoring, since the method was a bit hard to read.

fixes #15845

…mation (#15890)

As part of #15722, the decision was made to change the package.json files for
experimental packages to add 'alpha' identifiers. This ends up causing issues
for our ubergen-ed packages (i.e., aws-cdk-lib), which then try to include L1s
for these packages under the 'alpha' namespaces. Instead, switch (back) to
adding the alpha identifiers as part of the package transformation step.

Reverted the change to the pkglint rules, and re-ran `yarn pkglint` to update
the package.json files.

I also did some light refactoring, since the method was a bit hard to read.

fixes #15845

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*