chore: formally deprecate gpu-process-crashed event

[miniak]

Description of Change

Follow-up to #40089. Deprecated by #24367.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• relevant documentation, tutorials, templates and examples are changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: The gpu-process-crashed event on app has been deprecated.

[electron-cation]

🪦 Deprecation Checklist

🔥 New deprecations in this PR

• 📢 Are called out in docs/breaking-changes.md
• ⚠️ Use the deprecation helpers in lib/common/deprecate.ts to warn about usage (including events)
• 📝 Are marked as deprecated in the docs, using _Deprecated_ (including properties and events)

---

@electron/wg-releases: Please confirm these deprecation changes conform to our deprecation policies listed in docs/breaking-changes.md, then check the applicable items in the checklist and remove any non-applicable items.

[miniak]

@dsanders11 the gpu-process-crashed is kind of tricky to test, are you ok if I skip that?

[dsanders11]

@miniak, that's reasonable. I wonder if we should tweak our deprecation helper for events to warn when you bind an event listener, rather than when the event fires.

[release-clerk]

Release Notes Persisted

The gpu-process-crashed event on app has been deprecated.

[trop]

I have automatically backported this PR to "28-x-y", please check out #40195

[miniak]

@miniak, that's reasonable. I wonder if we should tweak our deprecation helper for events to warn when you bind an event listener, rather than when the event fires.

@dsanders11 that's a good idea