Fix incorrect nodeSelector label for deep health check (#382)

[FarhanTejani]

What's changing and why?

Closes #382

The deep_health_check_passed_nodes_only option generates an incorrect nodeSelector label deep-health-check-passed: "true" which doesn't match any actual HyperPod EKS node label, causing jobs to stay Pending indefinitely.

Fixed to use the correct label sagemaker.amazonaws.com/deep-health-check-status: "Passed" in both v1.0 and v1.1 templates and models.

Before/After UX

Before:
Jobs submitted with --deep-health-check-passed-nodes-only true generate:

nodeSelector:
  deep-health-check-passed: "true"

Pods stay Pending because no node has this label.

After:

nodeSelector:
  sagemaker.amazonaws.com/deep-health-check-status: "Passed"

Pods schedule on nodes that passed deep health check.

How was this change tested?

Unit tests pass (1029 existing + 3 new)

Are unit tests added?

Yes

Are integration tests added?

N/A

Reviewer Guidelines

‼️ Merge Requirements: PRs with failing integration tests cannot be merged without justification.

One of the following must be true:

• All automated PR checks pass
• Failed tests include local run results/screenshots proving they work
• Changes are documentation-only