fix(test): make metadata resource test immune to encoding

The prefix-encoded trie could occasionally encode the tested resource
name in a way that prevents the test to match. Using a "fake" version
number ensures a unique prefix is always present, and hence the tested
entry will never be encoded in unexpected ways.

Author: RomainMuller

packages/@aws-cdk/core/test/metadata-resource.test.ts

@@ -63,7 +63,7 @@ describe('MetadataResource', () => {
   test('includes constructs added to the stack', () => {
     new TestConstruct(stack, 'Test');
 
-    expect(stackAnalytics()).toContain('1.2.3!@amzn/core.TestConstruct');
+    expect(stackAnalytics()).toContain('FakeVersion.2.3!@amzn/core.TestConstruct');
   });
 
   test('only includes constructs in the allow list', () => {
@@ -141,11 +141,10 @@ const JSII_RUNTIME_SYMBOL = Symbol.for('jsii.rtti');
 
 class TestConstruct extends Construct {
   // @ts-ignore
-  private static readonly [JSII_RUNTIME_SYMBOL] = { fqn: '@amzn/core.TestConstruct', version: '1.2.3' }
+  private static readonly [JSII_RUNTIME_SYMBOL] = { fqn: '@amzn/core.TestConstruct', version: 'FakeVersion.2.3' }
 }
 
 class TestThirdPartyConstruct extends Construct {
   // @ts-ignore
-  private static readonly [JSII_RUNTIME_SYMBOL] = { fqn: 'mycoolthing.TestConstruct', version: '1.2.3' }
+  private static readonly [JSII_RUNTIME_SYMBOL] = { fqn: 'mycoolthing.TestConstruct', version: '999.2.3' }
 }
-