feat(remodel): generate index.ts and .jsiirc.json files

[madeline-k]

This PR modifies the gen.ts script that will run in aws-cdk-lib after the remodel.

1. I fixed a minor issue where the L1s were getting generated under aws-cdk-lib/lib/aws-service/service.generated.ts when it should be: aws-cdk-lib/aws-service/lib/service.generated.ts.
2. Generate index.ts files if they are not there
   a. In main, the only automation to do this exists in create-missing-libraries.ts, so I've lifted some inspiration from there.
3. Generate .jsiirc.json files if they are not there.
   a. In main, this is currently done by ubergen here, by applying a transform to the jsii targets in each package.json. This seems unnecesarily complicated to me.

Remaining todo:

• Run aws-cdk-lib's gen script at the end of the cloudformation spec update.sh script. This will cause the update job to check-in .jsiirc.json and index.ts files for new modules.

  Question: Should I just modify this in place on our branch code link? Or make the remodel tool do it?

• Mark create-missing-libraries.ts for deletion by the remodel tool

---

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

[gitpod-io]

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

[MrArnoldPalmer]

I fixed a minor issue where the L1s were getting generated under aws-cdk-lib/lib/aws-service/service.generated.ts when it should be: aws-cdk-lib/aws-service/lib/service.generated.ts.

So in our case I don't think we actually need the intermediary lib dir as that is not actually what the export paths are since they are defined in the package.json exports field. Also the top level lib directory serves to keep the large list of service directories out of the module root which makes it hard to work on imo. Otherwise LGTM

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ Features must contain a change to a README file.
❌ Features must contain a change to a test file.
❌ Features must contain a change to an integration test file and the resulting snapshot.

PRs must pass status checks before we can provide a meaningful review.