chore: in tests, publish both upstream and candidate versions of schema (#222)

We need 2 different versions of `@aws-cdk/cloud-assembly-schema`
versions available at the same time:

- The candidate version is used by `cdk-assets` (which doesn't bundle
it)
- The released version is used by `aws-cdk-lib` (which is used as part
of tests.

Requires updating to a new version of cdklabs-projen-project-types.

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

Author: rix0rrr

.github/workflows/integ.yml

@@ -1396,17 +1396,20 @@ new CdkCliIntegTestsWorkflow(repo, {
   testRunsOn: POWERFUL_RUNNER,
 
   localPackages: [
-    // CloudAssemblySchema is not in this list because in the way we're doing
-    // Verdaccio now, its 0.0.0 version will shadow the ACTUAL published version
-    // that aws-cdk-lib depends on, and so will not be found.
-    //
-    // Not sure if that will cause problems yet.
+    cloudAssemblySchema.name,
     cloudFormationDiff.name,
     cdkAssets.name,
     cli.name,
     cliLib.name,
     cdkAliasPackage.name,
   ],
+
+  allowUpstreamVersions: [
+    // cloud-assembly-schema gets referenced under multiple versions
+    // - Candidate version for cdk-assets
+    // - Previously released version for aws-cdk-lib
+    cloudAssemblySchema.name,
+  ],
 });
 
 new CodeCovWorkflow(repo, {