Inject some identifying properties to the gradle connection

[joshfriend]

Some builds/plugins depend on identifying gradle "sync" to configure their build properly

for example: https://github.com/joshfriend/spotlight/blob/d1903ac03a780278743a230f674d0c2aa7992204/spotlight-gradle-plugin/src/main/kotlin/com/fueledbycaffeine/spotlight/utils/IdeProperties.kt#L6-L12

[strangepleasures]

Hi,
Thank you for your contribution!

A few things I need to tell you about the state of Gradle support:

• The import mechanism we're currently using is very different from the one used by IntelliJ
• It lacks many features.
• We're going to replace it with a new implementation, which will be much closer to the one used in IntelliJ, but still might differ in some aspects

To avoid confusion, I would propose to add a new property named something like jetbrains.lsp.sync.version. We could set it to 1.0 for now and then upgrade to 2.0 after switching to the new mechanism.

Please tell me if this makes sense or not

[joshfriend]

Thanks! I understand that the implementation is different from that of IntelliJ and will likely remain so to an extent.

The reason I made this PR is that because our gradle build is so massive (~7000 projects) it takes a very long time and a lot of heap to load the entire project into an IDE. Both IntelliJ and this lsp extension use the gradle tooling API to configure the project and then retrieve information about the project from gradle. One way that we optimize this is by trimming projects out of settings.gradle when the project is loaded in an IDE. A user can select subsections of the repository to work on via some tool (e.g. spotlight which i linked in the description or other tools like focus). Our gradle build then looks during configuration phase to see if it is being invoked in a sync context (using the idea.sync.active property) to conditionally apply this behavior, which is not needed for builds because we use the configuration on-demand feature.

The reason I included the IntelliJ property is to provide some instant compatibility with these existing tools. To the best of my knowledge none of these tools use this flag to change the gradle model builders, only the project configuration phase, which is shared by both intellij and this lsp extension. I also added a new distinct flag in case it would ever be important to distinguish between the invocation contexts. Making the new property a version is a good idea, IntelliJ/Studio also inject their respective versions into the process.

[strangepleasures]

Thanks for the clarification. I think it's okay to postpone versioning for now, as we don't know what the versioning scheme is going to look like yet. It's never too late to add yet another property, right?