Update Frida script instructions for Frida 17

[cpholguera]

Added guidelines for using Frida 17 APIs exclusively and updated instructions for writing Frida scripts.

[cpholguera]

@IPMegladon would you mind taking a quick look? 🙏

[Copilot]

Pull request overview

This PR updates the Frida scripting instructions to align MASTG demo scripts with Frida 17’s API changes and clarify how contributors should write and run Frida-based demos.

Changes:

• Remove the old “Version requirement” section and instead introduce a dedicated “Use Frida 17 APIs exclusively” section.
• Add a mapping table that shows common pre–Frida 17 APIs and their Frida 17+ equivalents (exports, symbols, enumeration, memory access, and strings/byte arrays).
• Update the inspiration/examples section by dropping an outdated snippet that relied on deprecated Module.findExportByName usage.

[IPMegladon]

Another significant change is that the runtime bridges e.g. frida-java-bridge / frida-ios-bridge are no longer bundled with Frida.
The implication of this is that if you want to use these in scripts i.e. Java.* or ObjC.*, you will need to switch to a ts module that imports these modules.
Example of migrating existing js script:
https://github.com/AloneMonkey/frida-ios-dump/pull/200/changes
Example of updating existing ts module script:
oleavr/frida-agent-example@6cd18e7
For a new script, easiest is either:
Run frida-create -t agent or use https://github.com/oleavr/frida-agent-example

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[TheDauntless]

LGTM with minor modifications

[cpholguera]

Thanks again @IPMegladon, appreciate your help!