Cannot scan sites with self-signed SSL certs

.github/actions/find/dist/findForUrl.js に示されている失敗経路と、.github/actions/find/dist/index.js および bootstrap.js にある find アクションのエントリポイントから始めて、Playwright のページまたはブラウザーコンテキストがどこで設定されているかを追跡します。スキャンで ignoreHTTPSErrors の動作を有効にする方法を追加し、自己署名 HTTPS 証明書を使用するサンプル URL がジョブを中断せずに完了することを検証します。

Was giving this tool a little bit of a flex to see how it compares to our Lighthouse workflow, but found that it could not run against our testing environment, since the testing environment uses HTTPS with a self-signed SSL cert.

For context, we set up our testing environment dynamically in GitHub actions, and host it with docker/DDEV. When that environment is up, we can do Lighthouse, Playwright, and Selenium tests against that environment in GitHub CI to a similar degree that a developer could using their own computer.

When the local environment is set up, URLs that follow this pattern are available: https://test.ddev.site/my-test-page. When running this action against that example, we see an error like this:

Starting 'find' action
Preparing to scan https://test.ddev.site/my-test-page
node:internal/modules/run_main:107
    triggerUncaughtException(
    ^
page.goto: net::ERR_CERT_AUTHORITY_INVALID at https://test.ddev.site/my-test-page
Call log:
  - navigating to "https://test.ddev.site/my-test-page", waiting until "load"
    at findForUrl (/home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/dist/findForUrl.js:12:16)
    at async Module.default (/home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/dist/index.js:14:32)
    at async file:///home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/bootstrap.js:59:5
    at async file:///home/runner/work/_actions/github/accessibility-scanner/current/.github/actions/find/bootstrap.js:31:1 {
  name: 'Error'
}
Node.js v24.12.0

That error is thrown, and the rest of the job is completely skipped.

Maybe this action needs a new parameter so that the Playwright environment can use the ignoreHTTPSErrors option?