fix: take foreground visibility into account for win.isVisible() on macOS

[codebytere]

Description of Change

Resolves #16776.

Right now, our documentation says that for isVisible to return true for a given BrowserWindow, it must be "visible to the user." As @nickfujita pointed out, this should take into account whether or not a window is minimized, as well as whether or not a window is in the foreground (i.e. not obscured by other apps).

This PR therefore updates our win.isVisible() implementation on macOS to take occlusion and minimization into explicit account.

cc @MarshallOfSound

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue whereby foreground visibility of a window was not correctly taken into account for win.isVisible() on macOS

[MarshallOfSound]

Worth noting that the standard API [document.visibilityState](https://developer.mozilla.org/en-US/docs/Web/API/Document/visibilityState handles occlusions correctly and the current impl on Windows/Linux also uses the TrackOcclusionState helper for widgets in Chromium.

Strong 👍 on this change

[release-clerk]

Release Notes Persisted

Fixed an issue whereby foreground visibility of a window was not correctly taken into account for win.isVisible() on macOS

[trop]

I have automatically backported this PR to "5-0-x", please check out #17491

[trop]

I have automatically backported this PR to "4-1-x", please check out #17492