Added workaround for --isolatedModules inside of configuration files (#…

…39004)

This relates to a bug from issue #38957 found inside of the `with-cypress` example as a result of the recent typescript conversion. This issue can be resolved with adding `export {};` which prevents TypeScript from reading `.ts` configuration files from being read as legacy script files. This issue has been resolved on StackOverflow [here](https://stackoverflow.com/questions/56577201/why-is-isolatedmodules-error-fixed-by-any-import). More info on `--isolatedModules` can be read [here](https://www.typescriptlang.org/tsconfig#isolatedModules).

## Bug

- [x] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [x] Errors have helpful link attached, see `contributing.md`


Fixes #38597

examples/with-cypress/cypress.config.ts

@@ -5,3 +5,6 @@ module.exports = defineConfig({
     baseUrl: 'http://localhost:3000',
   },
 })
+
+// Prevent TypeScript from reading file as legacy script
+export {}

examples/with-cypress/cypress/e2e/app.cy.ts

@@ -18,3 +18,6 @@ describe('Navigation', () => {
     cy.get('h1').contains('About Page')
   })
 })
+
+// Prevent TypeScript from reading file as legacy script
+export {}

examples/with-cypress/cypress/support/commands.ts

@@ -35,3 +35,6 @@
 //     }
 //   }
 // }
+
+// Prevent TypeScript from reading file as legacy script
+export {}