Create a gated process for MFE release that's contingent on a threshold met for documentation

[jmakowski1123]

Problem

This has always been an issue with edx-platform, but it has unfortunately not been fixed with MFEs: a sysadmin needs to read the code to find out how many features work, or what particular configuration settings actually do. Furthermore, some MFEs are better documented than others. This makes it very difficult to streamline an upgrade pipeline, for example: one can never rely on documentation to be up-to-date on a new MFE.

Product/Platform Value

This has a direct impact on platform adoption: poor or lacking documentation not only hinders the process of including MFEs in releases, it makes them harder to use and to market.

Acceptance Criteria

The best way to achieve this is via the Build-Test-Release working group, having it act as gatekeeper. build-test-release#31 exists as a placeholder and is assigned to tCRIL.

Related or in-progress work

Contingencies

#426