Fix Idea plugin integration with GPMC

[avpotapov00]

In the PR #471 Move ideaPluginEnabled into the file scope lincheck-plugin compatibility was broken, as ideaPluginEnabled was calculated and assigned before the plugin could replace the result of the ideaPluginEnabled() method.
To keep caching and to give the debugger time to replace the return value, we make this property lazy, so it'll be calculated only on the first request.
In this case, the debugger has enough time to replace the function's return value.

[eupp]

@ivandev0 it looks like that ideaPluginEnabled was computed too early (during static initialization?), before the debugger had the opportunity to hijack ideaPluginEnabled() call. Because of this, the Lincheck plugin was not working. This PR makes ideaPluginEnabled a lazy property to delay its computation. Could you please check that lazy does not defeat the optimization?

[ivandev0]

Checked, performance still looking good.

[ndkoval]

Could you please leave a comment when the debugger becomes able to replace the ideaPluginEnabled() result?

[ndkoval]

@avpotapov00 I'm closing the PR but please address the issue later

[eupp]

There is an actual bug on Java 17 With Debugger Plugin (Lincheck)

[eupp]

It looks like the root cause of the issue was because beforeEvent() injection was not invoked for thread start/join events.
It resulted in exception being thrown on this line:

lincheck/src/jvm/main/org/jetbrains/kotlinx/lincheck/strategy/managed/ManagedStrategy.kt

Line 1960 in b1fbc37

error("Create nextEventId $nextId but last read event is $lastVisited, last read value is $lastIdReturnedAsCurrent")

I fixed it. As a nice bonus, now navigation to thread start/join trace points also works as expected in the plugin.

Another issue was because of the initialization order of eventIdStrictOrderingCheck and ideaPluginEnabled properties.
Property ideaPluginEnabled was dependent on property eventIdStrictOrderingCheck, but was initialized before it, leading to a subtle bug.
I reordered the properties declaration order for it to match the initialization order.

It looks like after the initialization order is fixed there is no need in lazy.
At least, I tested the plugin locally and everything seems to work.

@ndkoval could you also please test the plugin?