ci: remove concurrency from workflows

The `concurrency` configuration was removed from the `bench.yaml` and `test.yaml` workflows. Additionally, `FORCE_COLOR: 1` was added to the `env` section of `docs.yaml` and `release.yaml`.

This change simplifies the CI configuration by removing unnecessary concurrency settings that could potentially cause issues or unexpected behavior in certain scenarios. The `FORCE_COLOR` environment variable ensures consistent colored output in the CI logs for better readability.

Author: liblaf

template/.github/workflows/bench.yaml

@@ -16,10 +16,6 @@ on:
 env:
   FORCE_COLOR: 1
 
-concurrency:
-  group: ${{ github.workflow }} @ ${{ github.ref }}
-  cancel-in-progress: true
-
 jobs:
   metadata:
     name: Metadata

template/.github/workflows/docs.yaml

@@ -13,6 +13,9 @@ on:
   pull_request:
   workflow_dispatch:
 
+env:
+  FORCE_COLOR: 1
+
 jobs:
   build:
     name: Build

template/.github/workflows/release.yaml

@@ -9,6 +9,9 @@ on:
       - published
   workflow_dispatch:
 
+env:
+  FORCE_COLOR: 1
+
 jobs:
   build:
     name: Build

template/.github/workflows/test.yaml

@@ -18,10 +18,6 @@ on:
 env:
   FORCE_COLOR: 1
 
-concurrency:
-  group: ${{ github.workflow }} @ ${{ github.ref }}
-  cancel-in-progress: true
-
 jobs:
   metadata:
     name: Metadata