Rework way to help populate default certs without activating them

[bryanlandia]

Creating default certificates and activating them can be tedious, especially if the client is using signatories, as those images would have to be added manually to each course. However, some clients want to use HTML certificates on some courses but not all. Our approach to this so far has been to add the optional ACTIVATE_DEFAULT_CERTS FEATURE flag. Currently, if this is false, a default cert will be created and populated, but not activated.

This isn't working well. If the advanced setting, "Certificate Web/HTML View Enabled", is set to true, a "Request Certificate" button will always (it may also depend on the env flag CERTIFICATES_HTML_VIEW being True but that will always be the case) appear on the Progress page if the student has passed the course. When clicking that button, they will just get a "We're working on it" message, which will be confusing.

Instead, make a different Appsembler feature flag like ACTIVATE_COURSE_HTML_CERT_VIEW, defaulting to True. If this is set to False, the student should not see a button on the Progress page even if they have an active certificate.

This way the harder work of creating the certificate is automated, and the client who only wants certs for some courses has a single place to go turn them on.

To investigate:

• will this work as well to remove useless Request Certificate buttons from the student dashboard once we get that fixed for HTML certificates (edx-platform upstream issue)?
• alternate idea: don't activate certificates by default, but maybe make the Activate button also flip the advanced setting "Certificate Web/HTML View Enabled" switch to true if not already so.

[bryanlandia]

FYI @johnbaldwin @amirtds @bezidejni

[bryanlandia]

I think the problems here have been resolved other ways. Closing.