Fix ProjectTemplate build steps with new JDK

[sebastienros]

Fixes #55975

1. By running this step only on CI the ProjectTemplates local build doesn't work with a missing artifacts\obj\Npm.Workspace\Release\packagesToPack.json file.
2. Bump gradle because teh current version is not compatible with JDK 22
3. Reacted to gradle breaking changes: new maven plugin and DSL changes

After these changes eng\build.cmd -all -pack -configuration Release works on my machine.

[sebastienros]

I kept this because building the project keeps changing it back

[sebastienros]

Got warnings without that

[sebastienros]

This is the internal task that needs to be invoked to trigger publishing

[sebastienros]

IT's very probable I forgot something, didn't know what gradle was before this PR. At least I checked that the expected assets were generated:

The pom file:

<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.microsoft.signalr</groupId>
  <artifactId>signalr</artifactId>
  <version>9.0.0-dev</version>
  <packaging>pom</packaging>
  <name>com.microsoft.signalr:signalr</name>
  <description>ASP.NET Core SignalR Client for Java applications</description>
  <url>https://github.com/dotnet/aspnetcore</url>
  <inceptionYear>2018</inceptionYear>
  <licenses>
    <license>
      <name>MIT License</name>
      <url>https://opensource.org/licenses/MIT</url>
      <distribution>repo</distribution>
    </license>
  </licenses>
  <developers>
    <developer>
      <id>microsoft</id>
      <name>Microsoft</name>
    </developer>
  </developers>
  <scm>
    <connection>scm:git:https://github.com/dotnet/aspnetcore.git</connection>
    <developerConnection>scm:git:https://github.com/dotnet/aspnetcore.git</developerConnection>
    <url>https://github.com/dotnet/aspnetcore/tree/main</url>
  </scm>
</project>

[sebastienros]

Does the CI test the packages and their dependencies? The DSL wrt these dependencies has changed (compile, runtime, test) and I wonder if the final packages have the correct dependencies after this PR, and not too many (like test-only dependencies).

[mkArtakMSFT]

Thanks @sebastienros!

[sebastienros]

This is blocked on dotnet/dnceng#3093
The CI doesn't pass on macOS and linux because the JDK is too old and the opposite problem happens, which is they don't support the new Graddle.

[sebastienros]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.

[mkArtakMSFT]

@sebastienros is this still blocked? If so, can you please update the milestone of the associated issue so that it isn't sitting in an old milestone?