Correct issues related to unsupported parameter property in strip-only mode

[mho22]

Motivation for the change, related issues

While trying to run npm run local-package-repository I faced these type of Typescript errors

Version number df6471b7770cee7792040577 copied to clipboard
Use Ctrl+C to stop the server
node:internal/modules/run_main:123
    triggerUncaughtException(
    ^

file:///Users/mho/Work/projects/xdebug/wordpress-playground/packages/playground/blueprints/src/lib/v1/compile.ts:47
export class InvalidBlueprintError extends Error {
    constructor(message: string, public readonly validationErrors?: unknown) {
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
        super(message);

SyntaxError [ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX]: TypeScript parameter property is not supported in strip-only mode
    at parseTypeScript (node:internal/modules/typescript:63:40)
    at processTypeScriptCode (node:internal/modules/typescript:133:42)
    at stripTypeScriptModuleTypes (node:internal/modules/typescript:163:10)
    at ModuleLoader.<anonymous> (node:internal/modules/esm/translators:605:16)
    at #translate (node:internal/modules/esm/loader:546:20)
    at afterLoad (node:internal/modules/esm/loader:596:29)
    at async ModuleJob._link (node:internal/modules/esm/module_job:162:19) {
  code: 'ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX'
}

Node.js v22.21.1

Implementation details

Remove parameter properties in three files.

Testing Instructions (or ideally a Blueprint)

Run npm run local-package-repository successfully

[adamziel]

Thank you @mho22! I wonder if we can add an eslint rule that would keep that in check, I've broke it before in a similar way.