Task: Bump to Electron 32.3.3 for 1.133.0

[savetheclocktower]

In the past we've talked about being deliberate about how we catch up with recent Electron releases: aiming to jump at least one major version with each new release, but giving folks plenty of notice about ending support for older OS versions.

To be specific:

• Electron 33 will end support for macOS 10.15 (Catalina).
• Electron 38 will end support for macOS 11 (Big Sur). (It also changes Wayland behavior by automatically running as a Wayland app when appropriate without requiring an --ozone-platform flag; if that has impact on Linux users, we should warn them about it.)

With that in mind, I'm proposing this:

• Pulsar 1.133.0 should bump to Electron 32.3.3 — the latest release of Electron 32 — and should announce that it will be the last regular release to support macOS 10.15 (Catalina).
• Pulsar 1.134.0 should bump to Electron 37.10.3 — the latest release of Electron 37 — and should announce that it will be the last regular release to support macOS 11 (Big Sur). (If there are reasons to go slower than this, I'm happy to discuss them, but I can't think of any right now.)
• Pulsar 1.135.0 could be the one that brings us to the latest Electron version (currently 41)! I'm not aware of any newer releases that have ended support for any OS versions, so little would be stopping us from catching up at this point.

Let me know if this makes sense!

[asiloisad]

It's good that Pulsar is catching up with the latest version of Electron. This should be done more regularly in smaller steps.

[Daeraxa]

It seems that we may also have to update our node versions with it. On the releases it suggests that we can stay with node 20 for electron 33 but will need to be on node 22 for electron 38.

The next jump is at electron 40 needing node 24 which is still current.