"or condition for modules" can be turned on in production

make it so we can turn on this feature flag for everyone in
production. this means we have to remove the development flag.

closes CNVS-22780

test plan:
 - make rails think it's on prod, and not a test cluster
 - In the console: Account.site_admin.enable_feature!(:nc_or)
 - nc or should be forced on everywhere

Change-Id: I2988b020d619a93052aa0df1e11639cc3d446191
Reviewed-on: https://gerrit.instructure.com/61977
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
QA-Review: Clare Strong <clare@instructure.com>
Tested-by: Jenkins
Product-Review: Jon Willesen <jonw@instructure.com>

lib/feature.rb

@@ -75,6 +75,8 @@ class Feature
   #     enable_at: Date.new(2014, 1, 1),  # estimated release date shown in UI
   #     beta: false,          # 'beta' tag shown in UI
   #     development: false,   # whether the feature is restricted to development / test / beta instances
+  #                           # setting `development: true` prevents the flag from being registered on production,
+  #                           # which means `context.feature_enabled?` calls for the feature will always return false.
   #     release_notes_url: 'http://example.com/',
   #
   #     # optional: you can supply a Proc to attach warning messages to and/or forbid certain transitions
@@ -349,8 +351,8 @@ END
             display_name: -> { I18n.t('Enable "OR" Condition for Modules') },
             description:  -> { I18n.t('If enabled, modules will have the option to be marked as complete when only one of the requirements is met.') },
             applies_to: 'Course',
-            state: 'hidden',
-            development: true,
+            state: 'hidden_in_prod',
+            development: false,
             root_opt_in: true
         },
     'use_new_tree' =>