[Bug] Devlocity Build Scan publish failed

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.

### Environment

Linux

### EventMesh version

master

### What happened

Build Scan was introduced by https://github.com/apache/eventmesh/pull/4685. After upgrading the `com.gradle.enterprise plugin` to `com.gradle.develocity` in https://github.com/apache/eventmesh/pull/4926, the Build Scan can be published normally.

However, every workflow run after Jun 3 2024 23:09:36 HKT prompts Build Scan publish failed.

### How to reproduce

- The first workflow run that prompts Build Scan publish failed: https://github.com/apache/eventmesh/actions/runs/9352431276
- The last workflow run that successfully published a Build Scan: https://github.com/apache/eventmesh/actions/runs/9352414521

### Debug logs

```Java
Publishing build scan...

The Develocity server (ge.apache.org) rejected the request due to authentication being required.
If you are able to sign in to this server in a web browser, you can authenticate your environment by running the following task:

:provisionDevelocityAccessKey

Or see https://gradle.com/help/gradle-plugin-authenticating for additional help with authenticating your build environment.
```

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) *

Compare the first failing workflow run (9352431276) with the last successful run (9352414521), then inspect the repository's Gradle Develocity configuration and GitHub Actions workflow. Start with the authentication error and the upgrade from com.gradle.enterprise to com.gradle.develocity. Done means workflow runs can publish the Build Scan without an authentication failure.

Written by the indexing model from the issue text.