[MINOR] Add the redundancy value of the file to the build.Critical that warns us about bad health files.

MERGE REQUEST

MR Guidelines

Overview

Per @DavidVorick :

we need to distinguish better between health >1 and redundancy <1
a health >1 does not mean that the file is not coverable, it means the file will become unrecoverable if you don't repair it by the time your current contracts expire
redundancy <1 means the file is unrecoverable
if the file is recoverable but at high risk, you will see health >1 and redundancy=1

This means that the health status without the redundancy value is not enough for us to know, we need both. This MR adds the redundancy to the build.Critical about bad file health, so we can know more.

Example for Visual Changes

Checklist

Review and complete the checklist to ensure that the MR is complete before assigned to an approver.

• All new methods or updated methods have clear docstrings
• Testing added or updated for new methods
• Any new packages are added to Makefile and .gitlab-ci.yml
• API documentation updated for API updates
• Module README.md updated for changes to workflow
• Issue added to Sia-UI repo for new supporting features
• Changelog File Created

Issues Closed