chore: Move the items without tracking issues to the top

These are somewhat important to do before all the testing happens

Author: NickLarsenNZ

.github/ISSUE_TEMPLATE/early-pre-release.md

@@ -14,6 +14,17 @@ assignees: ''
 <!-- Update this with the parent tracking issue for the release -->
 Part of <https://github.com/stackabletech/issues/issues/xxx>.
 
+## Items which don't have a tracking issue
+
+- [ ] protoc updated in UBI Builder Dockerfiles (The earlier the better)
+- [ ] jmx_exporter (validate via hdfs-operator smoke tests)
+- [ ] krb5
+- [ ] tools (update the versions in version.py)
+- [ ] testing-tools (update the base, maybe keycloak)
+- [ ] statsd_exporter
+- [ ] csi-provisioner for secret-operator
+- [ ] csi-provisioner for listener-operator
+
 > [!NOTE]
 > Update the product versions based on what has been decided upon in the _Product Spreadsheet[^1]_.
 > Follow these rules when creating the tracking issues for individual images:
@@ -61,14 +72,3 @@ Part of <https://github.com/stackabletech/issues/issues/xxx>.
 - [ ] [Create issue from template: update-product-superset.md](https://github.com/stackabletech/docker-images/issues/new?template=update-product-superset.md)
 - [ ] [Create issue from template: update-product-trino.md](https://github.com/stackabletech/docker-images/issues/new?template=update-product-trino.md)
 - [ ] [Create issue from template: update-product-zookeeper.md](https://github.com/stackabletech/docker-images/issues/new?template=update-product-zookeeper.md)
-
-## Additional items which don't have a tracking issue
-
-- [ ] protoc updated in UBI Builder Dockerfiles (The earlier the better)
-- [ ] jmx_exporter (validate via hdfs-operator smoke tests)
-- [ ] krb5
-- [ ] tools (update the versions in version.py)
-- [ ] testing-tools (update the base, maybe keycloak)
-- [ ] statsd_exporter
-- [ ] csi-provisioner for secret-operator
-- [ ] csi-provisioner for listener-operator