chore: formally deprecate crashed and renderer-process-crashed events

[miniak]

Description of Change

Deprecated since #23096, #24410, #39494
Warnings fixed in #40090

Checklist

• PR description included and stakeholders cc'd
• 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 renderer-process-crashed event on app and crashed event on WebContents and <webview> have 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)
• 🧪 Relevant tests are updated to expect deprecation messages using the helpers in spec/lib/deprecate-helpers.ts

---

@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.

[dsanders11]

The crashed and render-process-gone events are on WebContents, not BrowserWindow.

[dsanders11]

Title of this PR should refer to renderer-process-crashed, not renderer-process-gone. If it's not too much effort, let's add tests which expect the deprecation messages (see the deprecation checklist from cation).

[miniak]

The crashed and render-process-gone events are on WebContents, not BrowserWindow.

@dsanders11 oops, I don't know how I missed that. Fixed now.

[miniak]

#40090

@dsanders11 Sadly the tests cannot be added easily as the tests don't share the instance of lib/common/deprecate with Electron itself. It's an unfortunate consequence of #35311. I will try to do something about it in a separate PR.

[miniak]

@dsanders11 We need to do this #40124

[miniak]

@dsanders11 the warnings are in main now

[dsanders11]

@miniak, I'm not sure if #40124 was necessary here. I added spec/lib/deprecate-helpers.ts in #39405 and used that for expecting deprecation warnings in previous PRs. The implementation there works around the internal module issue by listening to console.warn and the warning event on process and expecting the output there, instead of relying on the details of the deprecation module.

[miniak]

@miniak, I'm not sure if #40124 was necessary here. I added spec/lib/deprecate-helpers.ts in #39405 and used that for expecting deprecation warnings in previous PRs. The implementation there works around the internal module issue by listening to console.warn and the warning event on process and expecting the output there, instead of relying on the details of the deprecation module.

@dsanders11 I completely missed that somehow. Fixing in #40146

[release-clerk]

Release Notes Persisted

The renderer-process-crashed event on app and crashed event on WebContents and <webview> have been deprecated.