Reverting process invoker logs

[rishabhmalikMS]

Context

This PR addresses a race condition in ProcessInvoker.CancelAndKillProcessTree that causes InvalidOperationException ("No process is associated with this object") crashes in production.
📌 AB#2326727

---

Description

Removes risky process property access from trace logging statements in ProcessInvoker to eliminate race conditions. The changes include:

• Removed proc.Id access from CancelAndKillProcessTree trace logging
• Simplified ProcessExitedHandler to avoid proc.ExitCode access
• Updated ExecuteAsync completion logging to avoid proc.HasExited access
• Preserved all essential functionality while eliminating stability risks
• Reverted changes from below PRs
  • Adding process id in process invoker logs #5300
  • Ensure safe access to _proc in ProcessInvoker  #5327

---

Risk Assessment (Low / Medium / High)

Low Risk - This is a surgical fix that only removes non-essential logging statements. Core process execution functionality remains unchanged. The changes eliminate a known crash scenario without introducing new code paths or complex logic.

---

Unit Tests Added or Updated (Yes / No)

No

---

Additional Testing Performed

List manual or automated tests performed beyond unit tests (e.g., integration, scenario, regression).

---

Change Behind Feature Flag (Yes / No)

No

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

[rishabhmalikMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rishabhmalikMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rishabhmalikMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).