ci: rename workflows for Gitea UI readability

Switches the `name:` field on every workflow to the bulleted style:

  Tests · Go            (go-unit.yaml)
  Tests · UI            (ui-test.yaml)
  Tests · Integration   (integration.yaml)
  Deploy · Dev          (dev-deploy.yaml)
  Build · Prod          (prod-build.yaml)
  Deploy · Prod         (deploy-prod.yaml)

File names stay the same so existing path filters and any URL
references continue to work.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.gitea/workflows/deploy-prod.yaml

@@ -1,4 +1,4 @@
-name: deploy-prod
+name: Deploy · Prod
 
 # Placeholder for the production rollout workflow. Today it only proves
 # the manual entry point works; the actual `docker save | ssh prod

.gitea/workflows/dev-deploy.yaml

@@ -1,4 +1,4 @@
-name: dev-deploy
+name: Deploy · Dev
 
 # Builds the Galaxy stack and (re)deploys it into the long-lived dev
 # environment on the host running this Gitea Actions runner. Triggered

.gitea/workflows/go-unit.yaml

@@ -1,4 +1,4 @@
-name: go-unit
+name: Tests · Go
 
 # Fast unit tests for the Go side of the monorepo. Runs on every push
 # and pull request whose path filter matches a Go source directory.

.gitea/workflows/integration.yaml

@@ -1,4 +1,4 @@
-name: integration
+name: Tests · Integration
 
 # Full integration suite (testcontainers-driven, ~5–10 minutes). Heavy
 # enough that we do not run it on every push to a feature branch — only

.gitea/workflows/prod-build.yaml

@@ -1,4 +1,4 @@
-name: prod-build
+name: Build · Prod
 
 # Builds the production-grade Docker images and the UI bundle on every
 # merge into `main`, then saves the artifacts so a future

.gitea/workflows/ui-test.yaml

@@ -1,4 +1,4 @@
-name: ui-test
+name: Tests · UI
 
 # UI-side unit and end-to-end tests (Vitest + Playwright). The Go side
 # of the workspace is tested in `go-unit.yaml`. Both workflows can run