Add StikJIT for built-in JIT enabling

[CelloSerenity]

• Adds support for built-in JIT enabling on iOS 17.4+ via StikJIT. Requires a pairing file and LocalDevVPN, and it mounts DDI, enables JIT, and runs scripts. Pros: this is as close to seamless as it can get, and it’s better for UX for JIT enabling to be self-contained. It does everything StikDebug currently does and easier. We at StikDebug hope for this to become the new standard. Cons: the extension uses an extra app id, it doesn't work in LiveContainer yet due to lack of NSExtension handling, and you have to bundle idevice which increases binary size (about 5.5mb from the previous 16.7mb, about 33% bigger).
• Adds JIT enabling via StikDebug via url scheme on if StikDebug is present and device is running iOS/iPadOS 17.4+
• Adds a workflow for building unsigned ipas for testing on GitHub-hosted runners (intended to make testing changes on forked repos easier and faster). It should automatically skip itself in favor of your self-hosted runner on this repo.
• Note: I accidentally deleted the branch, closing Add StikJIT for in-app JIT enablement on iOS 17.4+ #269, so I guess this is a reopening

[OatmealDome]

Is there like a common copy of StikJIT in a submodule or something that all apps using it can share? Just wondering if I/you/anyone will need to manually recompile the xcframework in the future to update it.

[CelloSerenity]

@OatmealDome We host the pre-built xcframework in GitHub releases (https://github.com/StikDebug/StikJIT/releases) so maintainers can simply download and re-embed to update it.