chore: fix CloudFormation spec generation (#18441)

Two issues with the latest (v52.0.0) CloudFormation spec generation. First, we
are still combining "V2" libraries into single modules. This means new
generation services (like Inspector V2) are bundled into the existing (e.g.,
`@aws-cdk/aws-inspector`) modules.

Second, there was an issue with the Lightsail spec due to one of the properties
being "GetObject", which is not jsii-compliant. Introducing a hack here to add
an underscore in front of the Typescript property name (but not the generated
CloudFormation). Very open to better ideas, but this does work.

Once this has been pushed, we can regenerate the spec (now on version v53.0.0) as usual.

related #18305

----

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

Author: njlynch

tools/@aws-cdk/cfn2ts/lib/genspec.ts

@@ -237,6 +237,13 @@ export function cloudFormationToScriptName(name: string): string {
     }
   }
 
+  // There is (so far) one example of a property which has a "getter"-looking name
+  // (GetObject). This is not `jsii`-compliant, as it would conflict with generated getter method names.
+  // As an ugly hack, we prepend the Typescript name with an underscore.
+  if (/^Get[A-Z]/.test(name)) {
+    return `_${ret}`;
+  }
+
   return ret;
 }
 

tools/@aws-cdk/pkglint/lib/library-creation.ts

@@ -19,7 +19,7 @@ export interface ModuleDefinition {
 
 export function createModuleDefinitionFromCfnNamespace(namespace: string): ModuleDefinition {
   const [moduleFamily, moduleBaseName] = (namespace === 'AWS::Serverless' ? 'AWS::SAM' : namespace).split('::');
-  const moduleName = `${moduleFamily}-${moduleBaseName.replace(/V\d+$/, '')}`.toLocaleLowerCase();
+  const moduleName = `${moduleFamily}-${moduleBaseName}`.toLocaleLowerCase();
 
   const lowcaseModuleName = moduleBaseName.toLocaleLowerCase();
   const packageName = `@aws-cdk/${moduleName}`;