Refactor/cleanup tray related code after PR merged

[PikachuEXE]

Pull Request Type

• Bugfix
• Feature Implementation
• Documentation
• Other

Related issue

#6915

Description

Cleanup per #6915 (review)
Addressed stuff:

• Commented code
• Using .length as boolean -> .length === 0 / > 0
• If (!something) else -> if (something) else
• Move tray related code in main process to be behind process.platform !== 'darwin' so they should be removed on build time

Screenshots

Nope

Testing

Same as #6915

• Update _scripts/webpack.main.config.js from 'process.platform': '${process.platform}', to 'process.platform': '\'darwin\'', (replace `darwin with other values later
• yarn run pack && npx prettier@2.8.8 --write --no-config dist/main.js
• open dist/main.js
• Check setIgnoreDoubleClickEvents absent with darwin, present with other values

Desktop

• OS:
• OS Version:
• FreeTube version:

Additional context

[absidue]

Move tray related code in main process to be behind process.platform !== 'darwin' so they should be removed on build time (not idea how to test

The webpack config for the main file sets the value of process.platform to process.platform, so of your current machine/build machine, but you can also hardcode it to 'darwin', 'win32' or 'linux' to see what the build output looks like for other OS'. To make the build output more readable I use prettier 2 (3 and later don't seem to reformat files for some reason) as it's aggressive reformatting works quite well on mimified files e.g. npx prettier@2.8.8 --write --no-config dist/main.js.
As for navigating around the file faster, picking some things that won't change between input and output such as strings or methods provided by the runtime (electron, node, browser) e.g. isMinimized and searching for them in the output works quite well.

Those are just the steps I take when I want to look at the output, but if you find some better ways to do it, I am all ears :).

[PikachuEXE]

Updated testing section and locally tested (from previous macOS only testing