qa-report-app-admin: Reorder some sections for more clarity

Signed-off-by: Andre Moreira Magalhaes <andre.magalhaes@collabora.com>

content/guides/qa-report-app-admin.md

@@ -34,26 +34,6 @@ Debug logging from the service can be enabled via:
 debug: true
 ```
 
-### LAVA Authentication
-
-QA Report App uses shared secrets to authenticate legitimate LAVA callback
-submissions, which can be set in the config file:
-
-```yaml
-lava-callback-tokens:
-  - TOKEN-1
-  - TOKEN-2
-  - ...
-```
-
-Additionally, they can be set in the
-[environment](#environment-for-docker-compose).
-
-In order to obtain a new token, you need to create a new token in the LAVA UI
-(`API` → `Authentication Tokens`) for the user submitting the `notify` callback.
-The token's name should match the name set in the `notify`→`callback`→`token`
-property of the LAVA job definition YAML.
-
 ### Open ID Connect user login
 
 Users can login to submit manual reports.
@@ -81,6 +61,26 @@ For Gitlab, the `well-known-url` value is
 When set to `true`, the website will require users to be logged in to access
 any page. This is set to `false` by default.
 
+### LAVA Authentication
+
+QA Report App uses shared secrets to authenticate legitimate LAVA callback
+submissions, which can be set in the config file:
+
+```yaml
+lava-callback-tokens:
+  - TOKEN-1
+  - TOKEN-2
+  - ...
+```
+
+Additionally, they can be set in the
+[environment](#environment-for-docker-compose).
+
+In order to obtain a new token, you need to create a new token in the LAVA UI
+(`API` → `Authentication Tokens`) for the user submitting the `notify` callback.
+The token's name should match the name set in the `notify`→`callback`→`token`
+property of the LAVA job definition YAML.
+
 ### Filter displayed releases
 
 The `display` configuration section can be used to alter the minimal version to