* 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

Deadlock:
[AWTThread] awtLock -> SkiaLayer.dispose -> LinuxOpenGLRedrawer.dispose -> we are here -> lockLinuxDrawingSurface -> awtLock
[refreshRate updater thread] -> lockLinuxDrawingSurface -> we are here -> awtLock

We moved refreshRate to another thread, and check it only once a second, because it is not fast. I mistakenly thought in the past, that it is very slow on Linux (2ms), but it appears it was because of the awtLock itself. In the AWT thread it take 0.2ms, that is also slow for just one functions, but bearable, if it called only once every second.

Alternative is to subscribe to the native XRRScreenChangeNotifyEvent: https://www.x.org/releases/current/doc/man/man3/Xrandr.3.xhtml. But it seems X window system can have only one event queue associated with the window, and we already have one inside AWT, and we don't have access to it.

* `managedString` might be inlined and garbage collected before the beginning of JNI call

* add other missed `reachabilityBarrier`s

* align `nMakeFromBackendRenderTarget` signature with kotlin counterpart

* transfer `SurfaceProps` only via intArray

* rename `SurfacePropsObj` to `SurfacePropsInts`

* take `SurfaceProps` into account in `js/MakeFromBackendRenderTarget`

* update info about dpi-scale also on hardware layer paint

* `checkContentScale` on both of paints and on `update`

do not try to sync size if scale don't changed because it acquires draw lock

* remove misleading comment

* Set up max heap size and max metadata size for root project

We use the root project with Github Actions workflows.
However, the max metadata and the max heap size
are only set up in ./skiko subproject,
so they are not picked up in Github workflows,
which may lead to tests crashing on Linux

* Update Gradle for root and ./skiko

* allow to specify platform for adapter exclusion

* allow patterns in `not-supported-adapters.list`

* FL-16182 disable opengl on virgl

* encode list of excluded videocards in kotlin instead of resource file

by some reason loading resource file took about ~30-40ms

* Update kotlin to 1.7.20
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

* Update Skia

It is the same as m105-305b7c02-1, but with additional Windows ARM64 build

* Update gradle.properties

* Remove freetype

* Windows ARM support

Add skia.arch Gradle property.

We set it to `arm64` on CI to build a version for Windows ARM

* Fix build

* Exclude bytecode from skiko-awt-runtime-*.jar files

Previously, `skiko-awt.jar` and all of `skiko-awt-runtime-*.jar` files
contained the same bytecode. However, this led to duplication
of bytecode in Compose projects:
* `skiko-awt.jar` is a necessary API dependency of Compose/Desktop, which means
it is a runtime dependency as well;
* `skiko-awt-runtime-*.jar` is a necessary RUNTIME dependency of any Compose/Desktop project.

Thus, both `skiko-awt.jar` and `skiko-awt-runtime-*.jar` ended up in a runtime classpath of
any Compose/Desktop project, so the same classes were present in the runtime classpath twice.
This increased a final application image by approximately 1.1 Mb. Also, it led to
excessive ProGuard warnings, e.g. https://github.com/JetBrains/compose-jb/issues/2393

This change excludes bytecode from `skiko-awt-runtime-*.jar` artifacts, and adds
Maven dependency `skiko-awt-runtime-*.jar` -> `skiko-awt.jar`, so
many existing Maven/Gradle usages of `skiko-awt-runtime-*.jar` will continue to work.

SOFTWARE_FAST is not supported on macOS, so it should fallback to SOFTWARE_COMPAT

Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

* allow to change font rendering settings in paragraph

* add test

* rename

* fix js/native signatures

* workaround for kotlinjs