All internal components are renamed to Develocity

[erichaagdev]

This PR updates all internal references from Gradle Enterprise to Develocity.

Much of this is just a simple rename of ge and gradle enterprise to develocity, but there were a few occurrences where this wasn't the case. I have outlined any noteworthy and exceptional cases below:

• The bundled Maven extension was renamed from configure-gradle-enterprise-maven-extension to configure-develocity-maven-extension (it still configures both)
• All system properties passed to configure-develocity-maven-extension had their prefixes updated from com.gradle.enterprise.build-validation to develocity.build-validation
  • For Gradle, this has already been done, setting aside the fact that Gradle now configures the init script using environment variables
  • I made certain to not rename the system properties that are configuring the "Gradle Enterprise" Maven extension directly, such as gradle.enterprise.url and gradle.enterprise.allowUntrustedServer as these must remain for as long as we support using the GE Maven extension with the scripts
• All links pointing to documentation in Gradle.md or Maven.md has been updated from https://github.com/gradle/gradle-enterprise-build-validation-scripts/blob to the special short form redirect https://gradle.com/bvs
  • While this was not strictly necessary, it saves us one renaming step in the future and conveniently resolves When linking to documentation the short link is not always used #584

What remains are things that cannot yet be updated. This primarily includes all references to the repository, Gradle Enterprise distributions, bundled GE extension.

[ribafish]

LGTM 👍

[jprinet]

Great job, just a question about a GE artifact

[etiennestuder]

LGTM. Thanks, Eric.