Frida 17 introduced some breaking changes. Now, bridges are not bundled with Frida itself anymore, but instead they need to be explicitly imported. Unfortunately, outFile option can not be used when modules are imported, so it needs to be removed.
Also, TypeScript v6.0 completely removed the outFile option, so we would need to do this anyways when migrating to TS6.

Removing this option will make it so building no longer generates a single dist/index.js file (alongside index.d.ts and index.js.map), but instead every project file gets compiled to JS individually. Projects consuming frida-java-menu will break because of this. I'm still unsure if using a bundler is the right way to go, but for now I won't be using one.

With the Frida 17 changes, frida-gum now no longer contains type definitions for the Java namespace. Instead, they are now only in a separate package "frida-java-bridge". This package will be added in the next commit.

Since Frida 17, bridges are no longer bundled with Frida itself, but need to be explicitly imported.

In TypeScript 6, rootDir will no longer be inferred, but instead default to ".", so we need to explicity set it to the src directory.

For icons with transparency, both ImageView and WebView incorrectly replaced the transparent parts with white color

This commit fixes a few `java.io.IOException: Permission denied` exceptions that would be thrown when calling `Java.registerClass` not from within `Java.perform`.

Previously, it was only a devDependency, meaning it would not get automatically installed (and users would have to manually run `npm install` inside their `node_modules/frida-java-menu` folder)

In TypeScript 6.0, the default types value will be [] (an empty array), so we need to explicity set it to include types for Frida.