ci: fix release workflow; stop tracking tsconfig.tsbuildinfo

Two problems found by a release dry run:

- tsconfig.tsbuildinfo is a TypeScript incremental build cache that the
  frontend build rewrites, but it was committed. release:prepare refuses
  to run with a dirty working tree, so no release could ever complete.
  Untracked and ignored.

- The release step now runs with -Pci,gpg. maven-release-plugin is
  declared inside the gpg profile, so without activating it Maven fell
  back to the parent's pluginManagement version (3.0.1) and ignored the
  plugin's configuration entirely: the tag would have been named
  springdoc-openapi-3.1.1 instead of v3.1.1, autoVersionSubmodules would
  not apply, and release:perform would have deployed unsigned artifacts
  that Central rejects.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: bnasslahsen

.github/workflows/release.yml

@@ -72,9 +72,14 @@ jobs:
       - name: Test
         run: mvn $MAVEN_ARGS -Pci -T1C test
 
+      # -Pgpg is required, not optional: maven-release-plugin is declared inside
+      # the gpg profile, so without it the plugin falls back to the parent's
+      # pluginManagement version and none of its configuration applies —
+      # wrong tag name, no autoVersionSubmodules, and release:perform would
+      # deploy unsigned artifacts that Central rejects.
       - name: Release
         run: |
-          mvn $MAVEN_ARGS release:prepare release:perform \
+          mvn $MAVEN_ARGS -Pci,gpg release:prepare release:perform \
             -DreleaseVersion='${{ inputs.releaseVersion }}' \
             -DdevelopmentVersion='${{ inputs.developmentVersion }}' \
             -DdryRun=${{ inputs.dryRun }} \
@@ -87,4 +92,4 @@ jobs:
 
       - name: Clean up a dry run
         if: ${{ inputs.dryRun }}
-        run: mvn $MAVEN_ARGS release:clean
+        run: mvn $MAVEN_ARGS -Pci,gpg release:clean

.gitignore

@@ -147,3 +147,6 @@ Desktop.ini
 /CLAUDE.md
 /.claude/
 /default.profraw
+
+# TypeScript incremental build cache
+*.tsbuildinfo