chore: CI/CD and basic infrastructure for the IntelliJ Plugin

[kmruiz]

You'll see this PR is pretty big, as it adds the necessary infrastructure to build the plugin. There are three main blocks in this PR:

The build.gradle.kts files and the TOML dependency catalogue.

These are sections Project Structure and Gradle Plugins in the TD.

The CI/CD pipeline.

The structure is taken from VSCode but it's adapted to Gradle. It runs on GHA. We also adapted the changelog generation to use the JetBrains plugin for that, as it's their recommended approach.

Also, we added an example fitness function with JMH to do performance benchmarks before releasing.

Observability

All files under packages/jetbrains-plugin/src/main/kotlin are related to observability. The plugin now shows a small popup when activated (activates by default right now) and sends a telemetry event to Segment if possible.

[github-actions]

Coverage Report

Overall Project	92.5% -6.89%	✅
Files changed	92.42%	✅

File	Coverage
BuildInformation.kt	100%	✅
RuntimeInformationService.kt	100%	✅
TelemetryService.kt	100%	✅
LogMessage.kt	100%	✅
PluginActivatedProbe.kt	100%	✅
TelemetryEvent.kt	98.72% -1.28%	✅
SayHiListener.kt	0% -91.49%	🚫

[kmruiz]

This is the main build file. It would be like the package.json + webpack.config file for Java and Kotlin. Here we are defining the project dependencies and other subprojects.

[kmruiz]

This is the Gradle configuration file itself. It configures Gradle and how it runs, not the project.

[kmruiz]

Linting configuration. It will be used by spotless to run the linting checks.

[kmruiz]

This is the dependency catalogue. All dependencies will be declared here and used in the specific build.gradle.kts of the project.

[kmruiz]

This is a subproject Gradle build definition. In this case for the intellij plugin, so it adds all the specific repositories (of dependencies, like npmjs but for Java/Kotlin), plugins (helpers and additional functionality for Gradle) and dependencies.

[kmruiz]

This is a sample JMH benchmark. It will run the code in the function init a lots of times and generate statistics, like how many runs per second it could do.

[kmruiz]

This is an example startup activity. It runs once when a project is opened in IntelliJ. IntelliJ knows that this should be run because it's defined in the plugin.xml.

[kmruiz]

This is the plugin definition. We will add application listeners (classes that listen to other plugin events) and extensions (like the SayHiListener) here.

[kmruiz]

This file defines the settings for the project at the Gradle level. It allows to define subprojects, dependencies between projects and repositories for plugins.