strictVerify option is broken

[t3chguy]

It is of type boolean, states also that the default value is true.

If you provide true the signing breaks due to electron/osx-sign#344

And if you try to provide a string e.g. strictVerify: "all" and ignore the typescript error then the runtime schema validation fails.

• electron-builder  version=26.0.1 os=6.8.0-1020-azure
  • loaded configuration  file=/home/runner/work/element-desktop/element-desktop/electron-builder.ts
  ⨯ Invalid configuration object. electron-builder 26.0.1 has been initialized using a configuration object that does not match the API schema.
 - configuration.mac.strictVerify should be a boolean.
   -> Whether to let `@electron/osx-sign` verify the contents or not.
     How to fix:
     1. Open https://www.electron.build/mac
     2. Search the option name on the page (or type in into Search to find across the docs).
       * Not found? The option was deprecated or not exists (check spelling).
       * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root.
  failedTask=build stackTrace=ValidationError: Invalid configuration object. electron-builder 26.0.1 has been initialized using a configuration object that does not match the API schema.
 - configuration.mac.strictVerify should be a boolean.
   -> Whether to let `@electron/osx-sign` verify the contents or not.
     How to fix:
     1. Open https://www.electron.build/mac
     2. Search the option name on the page (or type in into Search to find across the docs).
       * Not found? The option was deprecated or not exists (check spelling).
       * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root.
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              at validate (/home/runner/work/element-desktop/element-desktop/node_modules/@develar/schema-utils/dist/validate.js:86:11)
    at validateConfiguration (/home/runner/work/element-desktop/element-desktop/node_modules/app-builder-lib/src/util/config/config.ts:239:3)
    at Packager.validateConfig (/home/runner/work/element-desktop/element-desktop/node_modules/app-builder-lib/src/packager.ts:354:5)
    at Packager.build (/home/runner/work/element-desktop/element-desktop/node_modules/app-builder-lib/src/packager.ts:362:5)
    at executeFinally (/home/runner/work/element-desktop/element-desktop/node_modules/builder-util/src/promise.ts:12:[14](https://github.com/element-hq/element-desktop/actions/runs/13109836482/job/36571249455#step:9:15))
error Command failed with exit code 1.

[mmaietta]

Let's see what happens in electron/osx-sign#344 as the default value of true should mean that you don't need to pass in strictVerify: true currently and can workaround the issue. To pass in a string, we'll need their type definitions updated.
https://github.com/electron/osx-sign/blob/757fa60716efd7310006153c55172fdcec46452a/src/types.ts#L175-L180

[t3chguy]

Sure, its just a safety thing of not relying on defaults and how they may change through breaking versions. Its good to be explicit with important things like code signing.