Use dnceng AzDO feed for maven

[akoeplinger]

This fixes CFSClean errors.

[Copilot]

Pull request overview

This PR consolidates Maven repository configuration for the SignalR Java client by migrating from public repositories (Maven Central and Gradle Plugin Portal) to Microsoft's internal dnceng Azure DevOps feed. The change centralizes repository management in settings.gradle using modern Gradle best practices and is intended to resolve CFSClean (Component Governance) errors.

Key Changes:

• Centralized all repository declarations in settings.gradle using pluginManagement and dependencyResolutionManagement
• Removed repository declarations from build.gradle buildscript and allprojects blocks
• Configured FAIL_ON_PROJECT_REPOS mode to enforce centralized repository management

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/SignalR/clients/java/signalr/settings.gradle	Adds pluginManagement and dependencyResolutionManagement blocks with dnceng AzDO feed configuration, enforces centralized repository management
src/SignalR/clients/java/signalr/build.gradle	Removes buildscript repositories block and allprojects repositories block, relying on settings.gradle configuration

Comments suppressed due to low confidence (1)

src/SignalR/clients/java/signalr/build.gradle:5

• The buildscript block declares a classpath dependency on spotless-plugin-gradle, but no repositories are configured for resolving this dependency. Buildscript dependencies are not resolved from the pluginManagement repositories in settings.gradle. You need to either add a repositories block within the buildscript block or convert this to use the plugins DSL instead. Consider replacing the buildscript approach with the plugins DSL by adding the plugin ID to the plugins block.

buildscript {
  dependencies {
    classpath "com.diffplug.spotless:spotless-plugin-gradle:6.6.1"
  }
}

[wtgodbe]

/azp run

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

[wtgodbe]

Components failure unrelated