FOLIO-4160: Enable mod-authtoken early in install*.json

https://folio-org.atlassian.net/browse/FOLIO-4160

Move mod-authtoken to the top of install-extras.json so that it gets installed early.

Then it is available when enabling a second module that requires a token to access a permission protected API of a third module.

Modules using authtokens don't have the authtoken okapi interface in their requires section of in their module descriptor because they don't use the mod-authtoken HTTP API but the token feature of Okapi. Therefore we need to use the install order to ensure mod-authtoken availability.

https://folio-project.slack.com/archives/CFQU1MF61/p1725977004958399?thread_ts=1725933118.184429&cid=CFQU1MF61

mod-authtoken requires mod-permissions and mod-users therefore we use this natural order:

1. mod-permissions
2. mod-users
3. mod-authtoken

Author: julianladisch

install-extras.json

@@ -3,6 +3,14 @@
     "id": "mod-permissions-6.6.0",
     "action": "enable"
   },
+  {
+    "id": "mod-users-19.4.0",
+    "action": "enable"
+  },
+  {
+    "id": "mod-authtoken-2.16.1",
+    "action": "enable"
+  },
   {
     "id": "edge-connexion-1.3.1",
     "action": "enable"
@@ -75,10 +83,6 @@
     "id": "mod-email-1.18.0",
     "action": "enable"
   },
-  {
-    "id": "mod-users-19.4.0",
-    "action": "enable"
-  },
   {
     "id": "mod-users-bl-7.9.0",
     "action": "enable"
@@ -251,10 +255,6 @@
     "id": "mod-quick-marc-6.0.0",
     "action": "enable"
   },
-  {
-    "id": "mod-authtoken-2.16.1",
-    "action": "enable"
-  },
   {
     "id": "mod-calendar-3.1.0",
     "action": "enable"