Update project build configuration and dependencies

[dzmpr]

Hi there!
I have some troubles with m2 bottom sheet navigator so I decided to add m3 bottom sheet navigator and solve this problem for me and for others. But when I started working on it I saw that voyager uses compose multiplatform 1.6.11 when I needed 1.7. One after another I'm ended up made some improvement to project build configuration and updated all dependencies (not only compose kmp).
So, what's have been done:

• Updated gradle and dependencies.
• Cleaned up project from redundant .gitignore and customer.proguard.pro files.
• Got rid of buildSrc and replace it with build-config included build. With buildSrc there are problems with using version catalogs and no pros.
• Split modules configuration to pluggable convention plugins to make configuration simpler and cleaner.
• Removed some unused or redundant dependencies (such as appcompat, compose-runtimeSaveable, compose-compiler, compose-animations, and maybe something else). Note: this compose dependencies are not multiplatform and only used in samples.
• Replaced com.benasher44:uuid dependency with kotlin stdlib implementation which is available from kotlin 2.0.
• Replaced compileOnly for compose dependencies with plain implementation as now seems all working fine but with compileOnly compiler threw warnings about js targets.
• Fixed js sample and some more minor fixes for samples.

What's I left behind:

• I can't figure out custom target hierarchy that voyager uses, so left it as is (with jvm("desktop") target which triggers compiler warning).
• Didn't update api dump, because I removed ExperimentalVoyagerApi from nonPublicMarkers (I consider this is a mistake, because it' actually public api, just experimental). So if you are okay with this I update api with additional commit.

I've tested all samples on android and following targets of multiplatform sample: js, wasm, macos (not sure what target).

So I'm waiting for review, and open for any questions if you have one.

[Vodes]

Fyi, this will currently cause an issue because compose expects (and forces) 0.23.2.
Seems to be a known issue https://youtrack.jetbrains.com/issue/CMP-5831