Zoom Fleet-maintained app relaunches Zoom after a patch even when it had no open window (macOS)

[jakestenger]

Body:
Fleet versions

• Discovered: Reported on a self-hosted Fleet instance. Version-independent — the defect is in the Zoom Fleet-maintained-app install script (darwin), synced from the manifest, not the Fleet server build.
• Reproduced: Not yet independently reproduced for Zoom specifically. Same root cause is code-confirmed and matches the already-filed Chrome bug (see More info).

Web browser and operating system: macOS (host-side FMA install script; not a web-UI bug)

---

💥 Actual behavior

After Fleet patches/updates Zoom on macOS, Zoom automatically launches once the install completes even when the user had no visible Zoom window open before the update.

🛠️ Expected behavior

Zoom should only relaunch if it had an active/visible window when the update began. Updates should complete silently if Zoom wasn't in use.

🧑‍💻 Steps to reproduce

These steps:

• Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
• Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.

1. Enable the Zoom Fleet-maintained app for update/patch on a team.
2. On macOS, leave a Zoom background/helper process running but close all visible windows.
3. Trigger the Zoom update via Fleet.
4. Zoom launches despite no window having been open.

🕯️ More info (optional)

The Zoom FMA install script gates relaunch on osascript -e 'application id "us.zoom.xos" is running' (sets ZOOM_WAS_RUNNING, then reopens with open -a "zoom.us" after installer). That check returns true for background/helper processes with no visible window, so Fleet relaunches Zoom even when the user had nothing open.

[allenhouchins]

Copied from #48639:

The one thing that needs to be checked is this might be the default behavior of the app installers themselves (to open once installed). There is also some slightly conflicting info in the report saying the app didn't have a visible window but background helper apps were running. It would be expected that those helper apps are quit and relaunched, which in some cases might bring an app window to the forefront upon relaunch.