Remove Develocity from GitHub Actions for now

Revert this commit once Develocity was configured in HV.

Author: yrodiere

.github/workflows/ci-report.yml

@@ -107,33 +107,13 @@ jobs:
         run: |
           ./mvnw $MAVEN_ARGS ${{ matrix.os.maven.args }} clean install \
           -Pjqassistant -Pdist -Prelocation
-        env:
-          DEVELOCITY_ACCESS_KEY: "${{ secrets.DEVELOCITY_ACCESS_KEY || '' }}"
-      # For jobs running on 'pull_request', upload build scan data.
-      # The actual publishing must be done in a separate job (see ci-report.yml).
-      # We don't write to the remote cache as that would be unsafe.
-      - name: Upload GitHub Actions artifact for the Develocity build scan
-        uses: actions/upload-artifact@v4
-        if: "${{ github.event_name == 'pull_request' && !cancelled() }}"
-        with:
-          name: build-scan-data-initial-${{ matrix.os.name }}
-          path: ~/.m2/.develocity/build-scan-data
 
       - name: Build code and run tests in container mode
         run: |
           ./mvnw $MAVEN_ARGS ${{ matrix.os.maven.args }} clean verify \
           -Pjqassistant -Pskip-checks \
           -am -pl :hibernate-validator-tck-runner \
           -Dincontainer -Dincontainer-prepared
-        env:
-          DEVELOCITY_ACCESS_KEY: "${{ secrets.DEVELOCITY_ACCESS_KEY || '' }}"
-      # Same as above, but for the build scan of the latest Maven run.
-      - name: Upload GitHub Actions artifact for the Develocity build scan
-        uses: actions/upload-artifact@v4
-        if: "${{ github.event_name == 'pull_request' && !cancelled() }}"
-        with:
-          name: build-scan-data-tck-container-${{ matrix.os.name }}
-          path: ~/.m2/.develocity/build-scan-data
 
       - name: Omit produced artifacts from build cache
         run: rm -r ~/.m2/repository/org/hibernate/validator