Avoid sharing folders for build outputs to enable proper up-to-date checks and use of gradle 8.1.1 (#717)

* Make rundown rendering bandaid(or not) fix to avoid incorrect scheduling problem

* Remove unneeded counter check.

* Extract magic value. Document it.

* Remove bandaid.

* Make right scheduling.

* Fix for path on double-dispatch during vsync-frame.

* Change logging a bit.

* Update doc

* Update doc

* Add comment on touchesCount, rephrase the body.

* Replace control flow with `also`

* Remove debug logs.

* Refactor 2 booleans into single enum.

* Simplify enum

* Replace Unit with empty body in `when` expressions.

* Replace comment style in function scopes.

* Make DrawSchedulingState private.

* Change comment style on private property.

* Add rationale behind drawSchedulingState initial value.

This reverts commit 85aef666.

Implement machinery for blocking draw dispatch before next vsync using synchronous wait on semaphore in native code.
Implement mechanism to prevent Metal command buffers overcommitment.

Minor tweak to the README

* Add method to MetalRedrawer for obtaining current UIView to which metalLayer is attached.

* Update caDisplayLink preferredFramesPerSecond when syncing metalLayer drawable size.

* Update skiko/src/iosMain/kotlin/org/jetbrains/skiko/redrawer/MetalRedrawer.ios.kt
Co-authored-by: dima.avdeev <99798741+dima-avdeev-jb@users.noreply.github.com>

---------
Co-authored-by: dima.avdeev <99798741+dima-avdeev-jb@users.noreply.github.com>

* Throw exception instead of force unwrapping Metal handles

* Update skiko/src/macosMain/kotlin/org/jetbrains/skiko/redrawer/MetalRedrawer.macos.kt
Co-authored-by: Ivan Matkov <ivan.matkov@jetbrains.com>

* Update based on review feedback

* Remove redundant this

* Remove unneeded imports

---------
Co-authored-by: Elijah Semyonov <elijah.semyonov@jetbrains.com>
Co-authored-by: Ivan Matkov <ivan.matkov@jetbrains.com>

* [awt.metal] Extract MetalDevice interface into .h file

* [awt.metal] Move context and renderTarget creation to ContextHandler

ContextHandler shouldn't depend on redrawer, since redrawer depends on ContextHandler

* [awt.metal] Use value class to hold MetalDevice pointer

* [awt.metal] Add docs for MetalDevice

* [awt.metal] Add simple docs for MetalRedrawer and MetalContextHandler

* [awt.metal] Use null instead of artificial pointer to 0

---------
Co-authored-by: Ivan Matkov <ivan.matkov@jetbrains.com>

* Update docker linux-emscripten-amd64

Install necessary libs + update emcc 3.1.35

* Update Dockerfile

* allow to configure logger in example applications

* use `layer.backedLayer` position and size as source to update CALayer

* non zero layer origin test

* Expose u_charDirection

* Move CharDirection to icu package

* Add doc comment for CharDirection

component listeners are performed to late so for absolute positioning we need to stick with `doLayout`

This reverts commit 2147b0e7.

* Add invalid unicode text that detects interop issue

* Remove utfToUtf8 function

* Fix JVM invalid unicode strings interop

* Update invalid unicode unit test

* Fix formatting and add more comments

1. Remove SkikoTouchEvent, we send all pointer events as SkikoPointerEvent now.

2. Add SkikoPointerEvent.Pointer that represents a separate touch/mouse

3. Implement multitouch for iOS/Android

* sometimes when we change scale via `EasyRes` or when we close/open lid and window is migrated to other screen `paint` is not called

see FL-18544

* customizable logger behaviour

* add debug logs in AWT layer

* migrate to m110

* use skia m110-ad42464-1

---------
Co-authored-by: Oleksandr Karpovich <a.n.karpovich@gmail.com>

* Add more prerequisites for building

* Xcode CLI is applicable to macOS only

* prevent usage of dangling pointer to `MetalDevice`

MetalRedrawer may be disposed during update which leads to use after free

* add test and comment

…on Windows

First off, I don't think there was any need for the repeated checks for device pixel ratio changes via checkContentScale because we should be able to rely on the graphicsContextScaleTransform property from AWT.

I removed the corresponding code and changed contentScale to directly return the platform-specific implementations from the toolkit/device. There's also no need to cache the value because the device and the graphics configuration already does it for us.

Secondly, there was a layout glitch on Windows when moving windows between monitors with different device pixel ratios. A fix has to happen directly in the JBR, but for now I created a semi-cheap workaround. See this issue and the linked ones for details: https://youtrack.jetbrains.com/issue/JBR-5259/Canvas-is-painted-at-the-wrong-position-after-dragging-JFrame-to-a-monitor-with-different-scale

* Update docs about development on Windows

Specified a more detailed manual how to install Visual Studio. I checked it on a clean PC.

* Update DEVELOPMENT.md

* Update DEVELOPMENT.md

* added performance test with clocks

ignore tests with clocks

* use simple logger instead of printlns

* checked that we call `finishRecording` at the same picture that we called a `beginRecording`

* make `Logger` internal

* disable assertions in rendering performance test with content; otherwise it might be too flaky

* unignore `FPS is near display refresh rate (multiple windows with clocks)`

Co-authored-by: Steyn Geldenhuys <steyn.geldenhuys@sieveo.com>

... and make software renderers respect the pixel geometry

We accidentally didn't prepare the SurfaceProps into an IntArray when passing them down into the JNI in the Windows version. The memory layout must have accidentally matched between both representations on Windows 10, but it doesn't work on Windows 11 for some reason. This is the proper fix.

* Use gradle 7.6

* add plugin repositories

* add plugin repositories