Some exotic v1 stacks aren't identified when aws-cdk is listed by itself in the Modules property

[brandondahler]

Stacks we have deployed contain a very limited set of information in the CDKMetadata modules section but are notably v1.

The complete CDKMetadata resource in our stack is:

  CDKMetadata:
    Type: AWS::CDK::Metadata
    Properties:
      Modules: aws-cdk=1.119.0

This appears to not be matching because the code assumes that @aws-cdk/core will be included in the list of modules on this line

[brandondahler]

I speculate that this might happen when the @aws-cdk/core or monocdk version is less than 1.93, but the aws-cdk cli package used is newer; however, I haven't looked closely to see if this is the case.