fix: intelliJ 2022.3 breaking plugin + lsp server exceptions

[TomerFi]

Usually I prefer smaller PRs, but this one had to include multiple modifications to make everything work well.

Closes #79, Closes #89 
Fixes #76, Fixes #81, Fixes #91, Fixes #92 

Worth noting:

• Bump IntelliJ plugin version to 1.13.2 based on docs recommendation.
  view docs
• Bump Java version to 11, we target intellij version to major 2021.1 which have been migrated to java 11.
  view article
• Storage configuration, file has been deprecated and replaced by value.
  view docs

Tested locally with versions:

• 2021.1 (our minimum target)
• 2022.2
• 2022.3 (the latest version)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[github-advanced-security]

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

[TomerFi]

@jeffmaury please review this when you're available.

[jeffmaury]

Too much unrelated stuff in one plugin.Please split per concern: one commit = one PR

[TomerFi]

I respectfully disagree.

Unless we have a technical requirement for that. Then this can be achieved by doing Rebase+Merge.

This is a small PR, I don't see value in converting it to 8 PRs.
But if it's a blocker for you as the repository maintainer, I'll do it.

Please let me know your decision.
Thank you.

[jeffmaury]

It's not a matter of merging/rebasing but this is how we work together. The policy on this project has been to provider one PR per concern/issue, please adapt.

[TomerFi]

Let's agree to disagree on this.

Regardless, if this is how you prefer to work on this project, I'll split this into 8 PRs, no problem at all.

Thank you.