* 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

This was enabled in Toolbox, and it seems work without issues.

When we throw RenderException, we fallback to the next render API.

* Fix crash on Windows when there is no compatible DirectX adapter

Fixes https://github.com/JetBrains/skiko/issues/582

* Fix mistake

We need to also catch IllegalStateException. It is said in the JavaDoc and mentioned here:

https://github.com/JetBrains/compose-jb/issues/2098#issuecomment-1234693644

* check preconditions of `FontRunIterator::consume` as it's in SkShaper.cpp; remove code duplication

* check `ubrk_following` return value, otherwise it may lead to hanging in `FontRunIterator::consume`

* Fix getting text from clipboard

Sometimes, internal AWT implementation can't properly parse the clipboard data.

getData's docs say that it can throw IOException

* Return UnsupportedFlavorException

* add iosSimulatorArm64 target
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

From skia sources:
DXGIGetDebugInterface1 is defined in dxgi.lib.
But this API is tagged as a development-only capability which implies that linking to this function will cause the application to fail Windows store certification
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

Recently it was added to CI, and wasn't properly tested

https://docs.microsoft.com/en-us/cpp/build/reference/fs-force-synchronous-pdb-writes

It was suggested by the error message in a Teamcity build
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

* fix RunRecordClone data layout in debug mode

* migrate to skia chrome/m105

* fix tests

* allow to retrieve text from Paragraph

* add missing includes; use c++17 on windows; bump skia version

* Move some files from jvmTest to awtTest

Because they depend on AWT classes.

jvmTest is shared between AWT and Android implementations

(cherry picked from commit 616934ce)

* Move jvmMain -> awtMain

This reverts commit 616934ce.

Because they depend on AWT classes.

jvmTest is shared between AWT and Android implementations

* SkiaLayerAnalytics - send events for different steps of rendering

It will help us to detect GPU's, on which we have crashes. After we compare two events, we can investigate GPU, and if the issue only in it, we will add it to not-supported-adapter.list

The plan to integrate this analytics to Toolbox.

* Fix build

* Disable performance tests on CI

CI can have different performance for different runs. Currently we have failing vsync tests for Windows

* Fix analytics test on github actions

* Fix CI

Angle is a stable Skia renderer, which is used by Chromium instead of direct DirectX, OpenGl, Metal renderers. It is considered more stable, but needs the ~30mb binary library. Angle mimics OpengGL ES and calls corresponding DirectX/Metal API's.

Angle support wasn't fully implemented, there just a bunch of class prototypes in the source code, that gets in the way during refactorings.

Deleting it for now, until we decide to fully support it. When we decide it, we can look at git history.

- Make SkikoProperties public, and don't cache the values, so users can change properties in runtime

- Deprecate skiko.directx.gpu.priority and skiko.directx.gpu.priority, introduce skiko.gpu.priority. There is no need in separate priority for macOs/DirectX

- Fix skiko.fps.enabled property

* skString c_str contains string encoded in UTF8, but it was treated as UTF16

* ensure that managedString doesn't collect til the end of JNI call, also close manually at the end

Also fix keyEvent leaks on iOS (#560)

* Another method to parse font features

Needed for Compose. I compare it with Android, and Android/Compose by documentation uses this format without quotes: ttps://www.w3.org/TR/css-fonts-3/#font-feature-settings-prop

* Fix CI

t seems there are some pending transactions, which weren't flushed after we remove the metal layer

Kotlin 1.7.0 introduced some changes related to kjs module names.

Therefore, we need to override the moduleName to avoid name collision with a different skiko.js file
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

* Add binding for SkGraphics methods

* Add binding for SkGraphics methods in nativeJsMain

* Add smoke tests for SkGraphics bindings

* explicitly resolve java.awt.Graphics reference

* fix external symbol names for SkGraphics bindings

* Dynamically load GetDpiForWindow to support Windows before 10

* Dynamically load GetDpiForMonitor to support Windows before 8.1

* Update drawlayer.cc
Co-authored-by: Igor Demin <igordmn@users.noreply.github.com>

* jvm crash when input array is null

* makes `bytes` non-null

It is already public in the targets