fix: use correct prefix for build and ci dependencies (#103)

# Description

- use `ci` prefix for the release process defined in `.release`
- use `build` prefix for Maven and related plugins
- use the correct prefix for dependencies used in the
`dependencyManagement` section

# Verification

Not checked

Author: Matthias Kay

.config/cspell.json

@@ -8,6 +8,7 @@
     "javadoc",
     "javadocs",
     "oidc",
+    "projectlombok",
     "Repology",
     "sonatype",
     "tflint",

default.json

@@ -47,7 +47,21 @@
       "description": "Use the `test` prefix for Maven test dependencies."
     },
     {
-      "matchFileNames": [".github/workflows/*"],
+      "matchPackageNames": ["org.junit:junit-bom"],
+      "semanticCommitType": "test",
+      "description": "Test dependencies used in the dependencyManagement section are identified as production dependencies."
+    },
+    {
+      "matchPackageNames": [
+        "maven-wrapper",
+        "org.apache.maven.plugins:*",
+        "org.projectlombok:lombok"
+      ],
+      "semanticCommitType": "build",
+      "description": "Build dependencies not identified automatically."
+    },
+    {
+      "matchFileNames": [".github/workflows/*", ".release/*"],
       "semanticCommitType": "ci",
       "description": "Use the `ci` prefix for workflow dependencies."
     }