[SLES-2826] Reproducing AAS Restart Named Pipe Overlap Issue [Do Not Merge]

[Lewis-E]

Add ProcessSupervisor and NamedPipeHealthCheck diagnostics for SLES-2826

Adds [aas-repro] INFO-level log lines to make the pipe-collision failure mode observable without DD_TRACE_DEBUG=true:

ProcessSupervisor:

• Health state transitions logged at INFO on every change
• Spawn logged with jvm_pid for cross-process correlation
• Process start logged with child_pid and faults_reset_to_0
• Process exit logged with exit code and resulting health state
• Terminal fault break logged with fault count

ExternalAgentLauncher:

• Supervisor creation logged with path, pipe name, and jvm_pid

NamedPipeHealthCheck (previously silent):

• First-check entry logged with pipe name
• NEVER_CHECKED → READY_TO_START logged with retry count
• NEVER_CHECKED → HEALTHY logged with warning (orphan risk)
• Ongoing HEALTHY → READY_TO_START logged when pipe disappears

What Does This Do

Motivation

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors

Jira ticket: [PROJ-IDENT]

Note: Once your PR is ready to merge, add it to the merge queue by commenting /merge. /merge -c cancels the queue request. /merge -f --reason "reason" skips all merge queue checks; please use this judiciously, as some checks do not run at the PR-level. For more information, see this doc.