[LinuxConsumption] Mark Container Unhealthy During Failed Specialization

[Tonewall]

Issue describing the changes in this PR

WI: https://msazure.visualstudio.com/Antares/_workitems/edit/32785404/

resolves #9663

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

[jviau]

@Tonewall is this change still needed? With the health checks recently added, the system will not report healthy until we get successful script host started. So if any point of specialization fails before starting the script host, the instance will remain unhealthy.

This should be tested though. Also if there are any components here worth their own health check (like checking if azure files is mounted successfully), you can open a new issue requesting they be implemented.