Add jvm, js and wasmJs targets

[frogggias]

Extends KMP support to JVM, JS, and JS WASM targets, closes #2

• urlencoder:1.6.0 dependency is upgraded because it adds more KMP targets
• Changes in Buffer, CharArrayBuffer, and ParserStateMachine are made because of the signature clash on the JS platform.

[frogggias]

Also, I updated the publishing configuration and the Readme accordingly - verified on the local maven repository on the KMP project (JVM, Android, JS, WASM JS) and pure Android project.

Unable to verify that configuration is working for publishing to mavenCentral.

[davidvavra]

I'm not sure about changing the artifact name. Is it because the code doesn't have any Android-specific dependencies and it's pure JVM code?

[frogggias]

Exactly, there is nothing Android-specific right now. The whole Android-specific implementation can be removed, with the removal of minSdk limitation as a positive side effect.

Several generated modules for different platforms should be resolved correctly when using root spayd-kmp.

spayd-kmp
spayd-kmp-iosarm64
spayd-kmp-iossimulatorarm64
spayd-kmp-iosx64
spayd-kmp-js
spayd-kmp-jvm
spayd-kmp-wasm-js

For some reason, it doesn't work this way when using the deployer publishing, but works with publishToMavenLocal task and default shared-* artifacts.

I will investigate it further.

[davidvavra]

OK, I agree with removing Android specific implementation and changing the artifactId.

We are using MavenDeployer plugin for deploying to Central. It also support local deploy, so please try to deploy locally and see what artifacts in generated.

When it will be published to Central, there will be just one artifact or multiple?

Also, I'm not sure how it works in Javascript world with the KMP & dependencies - should we deploy to some JS specific repository like NPM?