docs: add IPC doc

[erickzhao]

Description of Change

See https://electronjsorg-new-pr-145.herokuapp.com/docs/latest/tutorial/ipc/ for preview.

Adds tutorial on IPC.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is 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: none

[miniak]

you are undoing changes from #31752

[erickzhao]

Good catch @miniak, I'll address those soon.

[VerteDinde]

This is great work, will help a lot of people! 👏 Good to go once the changes are addressed

[Toinane]

Looks great 👍

[jkleinsc]

Merging as change is docs only, so Windows CI does not need to apply to this PR.

[release-clerk]

No Release Notes

[trop]

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

[Gyeop]

I don't think ipcRendererEvent has a reply method. Could you please check it?
event.reply('counter-value', newValue) -> event.sender.send('counter-value', newValue)

[trop]

@erickzhao has manually backported this PR to "18-x-y", please check out #33748

[Cono52]

I would love if a small paragraph/warning was added to this with regards to the limitations of using the IPC process for real-time levels of performance.
I only have anecdotal expeirence of getting real-time data i.e. a high-frequency websocket off of the main-thread and move it to the place the main thread was sending it to, via IPC. This, way we avoided the structure copying of all these objects and whatever else happens which would slow everything down. My main rule has usually been use it only for "user initiated" message passing, as oppose to hooking it up to something firing 10 times a second.