Restore test settings before after_suite to fix cross-suite leak

after_all ran after_suite before restoring the per-suite settings snapshot.
Suites that enable a setting in before_suite (e.g. test_rack_attack sets
enable_security) and do privileged cleanup in after_suite (deleting users)
then ran that teardown with the setting still active -> WriteAccessDeniedError.
Because after_suite raised, restore_settings never ran, so enable_security
leaked into every later suite (data-setup WriteAccessDenied, 401s on public
routes). Restore first so teardown runs with settings rolled back and a raising
after_suite cannot leak.

Author: alexskr

test/test_case.rb

@@ -178,8 +178,12 @@ def before_all
   end
 
   def after_all
-    after_suite
+    # Restore settings BEFORE after_suite: teardown often does privileged
+    # cleanup (deleting users/ontologies) that must run with the suite's
+    # settings rolled back (e.g. security off). Restoring first also means a
+    # raising after_suite can't leak a flipped setting into the next suite.
     restore_settings(self.class.instance_variable_get(:@suite_settings_snapshot))
+    after_suite
     super
   end