Enable Public and Approved options only when ADW is activated

[giohappy]

A recurrent question is why the "Public" and "Approved" options do not seem to affect resource visibility.
The question is legit because they actually do not affect visibility unless the ADW options are activated.
The options are RESOURCE_PUBLISHING and ADMIN_MODERATE_UPLOADS, which are False by default.

The combinations of these options activate distinct (and very specific) behaviours that go behind the generic term of "Advanced Workflow". You can read about the ADW here and an active discussion in GNIP 103.

Back to the "Public" and "Approved" options, they do not affect visibility or permissions directly, even when the ADW is activated. What they do is driving "state transitions" when the resource is saved. If the two options are changed when a resource is saved, a set of side effects is triggered, including automatic changes to the permissions of users and groups, depending on their roles and the combinations of the ADW settings.
This is pretty complicated and hard to follow, and this is one of the reasons we're proposing to deprecate the current ADW implementation in favour of a simpler logic.

Aside from the discussion on ADW itself, we think the "Public" and "Approved" should be available only when they make sense, i.e., when ADW is active. Specifically, the proposal is to:

• make the "Published" options available only if RESOURCE_PUBLISHING is True
• make the "Approved" options available only if ADMIN_MODERATE_UPLOADS is True

It will help clarify their (current) role.

[giohappy]

The plan is to expose two new settings inside the JavaScript __GEONODE_CONFIG__ to allow the client to conditionally render the two options inside the Settings panel.

The two boolean settings are isPublishedOptionEnabled and isApprovedOptionEnabled

The context_processor can define the two new settings by reading the RESOURCE_PUBLISHING for the former and ADMIN_MODERATE_UPLOADS for the latter