Coverage goal for testing the repo

[aatifsyed]

While release strategy might be adjusted later, once the library/binary matures, I do believe that we should set high standards to new repositories with regards to test coverage. It's challenging to impose it on Forest at this stage, but fresh software should be designed with automated testability-first, otherwise it will meet the definition use of legacy code just as it lands on main - legacy code being code without tests. Should we assign at least a soft coverage goal for the new repositories? That is to say, aim to have at least XX coverage (not enforced)?

@LesnyRumcajs in Slack