Remove issue health status from Geo process

Why is this change being made?

We experimented with using the issue health status feature in our build board issues, but it never felt quite right. As a result, I did not keep up with the practice of using the health statuses. Improved visibility and escalation of long-running work was the main goal for trying health statuses. More consistently prompting epic owners and assignees for updates during or before the scheduling call has been sufficient in this regard.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.