Remove conditional views in Golden Config

[jtdub]

Closes #842.

1. Removes conditional based UI views
2. Allows configurations to be updated in the Golden Config Settings UI.

Navigation views display all options regardless of what is enabled or disabled:

Golden Config Settings displays whether backups and intended are enabled:

Creating and Updating Golden Config Settings in the UI:

Reading the Golden Config Settings in the UI.

[jeffkala]

• content_template.html - Does have some conditional views logic as well. But perhaps its one that makes some since since its on the device detail side. Just notating here for review purposes for now, no action right now.
• goldenconfig_list.html - Has some conditional view logic that needs to figure out if we should remove as well.

[jeffkala]

AS far as this concern: "UI-based configuration settings would apply to each device individually within a dynamic group, rather than checking the configuration globally once."

I don't expect this to cause much performance issue as we already have function get_device_to_settings_map that does most of this work. I think its still one call to that function to create the map and then its a call to the map.

[jeffkala]

List view for GC settings has two different types of checkbox.

Also not sure we really need all these in the table view.

[jeffkala]

Doing a full review of this today.

[jeffkala]

@jtdub here's my first review. Many seems like we need to harden the checks before things execute based on GC setting (setting) variable.

1. GC setting for only backing up devices with everything else turned off.
   1. The assumption would be you don't need SOT_AGG query. Gives an error.
   2. Running the intended job on the device where intended is disabled gives error E3018: Missing the required global setting: jinja_path_template.
      1. Would be good to give a better error (intended generation is not enabled or similar)
   3. Similar with all the jobs, odd errors are given when jobs are run against device that doesn't have that "setting" enabled.
2. If a device previously had been in-scope for say "config compliance" and you change it to out of scope the device still shows in the config compliance list view
   1. May need some kind of cleanup? (TBD)
   2. Or just document as part of an migration guide
3. When config-plans are disabled. You can still create a config plan for a out of scope device. (Might be due to previous bullet point)
   1. You can also still deploy a config plan when deployment is disabled.
4. Generally jobs run that include elements of settings that are currently turned off the error Missing the required global setting: may need to be more verbose Missing the required global setting as the golden config setting is disabled or something.
   1. Seems like proper log entries for "feature x is disabled" works for the backup job when backups are disabled for a device.