[Bug] Chromium leaves remnants of openDatabase/webSQL support, which is detected by fingerprintJS

[chopen]

Describe the bug
When using chromium the window.openDatabase property exists and is a callable function. (BAD)

When using chrome proper, that property is missing. (GOOD)

FingerprintJS retrieves the presence and status of this property. I noticed it was a critical data item being used to block logging in to some top ecommerce sites. Here is a chromium issue discussing removal of it from chrome, safari, et al. However it appears by default it is still present in chromium builds which come down with full PPTR.
https://bugs.chromium.org/p/chromium/issues/detail?id=695592

Removing it similar to the following fixed my issues:
Code Snippet

    await page.evaluateOnNewDocument(function regCallback() {
      // ******************************************************************************
      // REMOVE Open Database - Chromium webSQL legacy shows chromium vs chrome
      // It seems that it is supposed to be removed, but this remnant is left on the window
      // See: https://bugs.chromium.org/p/chromium/issues/detail?id=695592
      // ------------------------------------------------------------------------------
      (function () {
        delete window.openDatabase;
      })();
      // ******************************************************************************
    });

Versions
System:
OS: Linux 5.19 Ubuntu 22.10 22.10 (Kinetic Kudu)
CPU: (8) x64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Memory: 27.64 GB / 31.22 GB
Container: Yes
Shell: 5.2.2 - /bin/bash
Binaries:
Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
npm: 9.6.7 - ~/.nvm/versions/node/v18.13.0/bin/npm
npmPackages:
puppeteer: ^20 => 20.9.0
puppeteer-extra: ^3.3.4 => 3.3.6
puppeteer-extra-plugin-stealth: ^2.11.1 => 2.11.2
puppeteer-intercept-and-modify-requests: ^1.3.0 => 1.3.0