fix(update): exclude ancestor PIDs from running-process check

[jrob5756]

Problem

On Windows, conductor update reports its own launching shim as another running Conductor process:

conductor update
Checking for updates…
Warning: 1 other Conductor process is running:
  • PID 299112: conductor.exe

The shim conductor.exe is a separate process from the Python interpreter that runs this code, so os.getpid() does not match the shim's PID — the shim was incorrectly flagged.

Fix

Walk the full ancestor process chain and exclude every PID along the way:

• Add _get_self_and_ancestor_pids() — returns {getpid(), getppid()} plus every ancestor reachable via the parent-PID map.
• Add _build_parent_pid_map() — uses wmic on Windows and ps -axo pid=,ppid= elsewhere. Returns {} on any failure.
• _find_running_conductor_processes() now consults the excluded set on both platforms.
• Defensive cycle detection prevents infinite walks if the parent map is malformed.

Tests

Adds 6 new tests in TestAncestorPidExclusion:

• self_pid is in excluded set
• getppid() is in excluded set
• ancestor chain via parent map is excluded
• empty parent map falls back gracefully
• cyclic parent map terminates the walk
• ancestor reported by ps/tasklist is filtered out

All 68 update tests pass; lint and typecheck clean.