Support a way to completely block-off analysis and use that when the target is executing

Version and Platform (required):

• Binary Ninja Version: [e.g. 4.0.4000-dev] (if version is stable, please also test the latest development build via the "Update Channel" option)
• OS: [e.g. Ubuntu Linux]
• OS Version: [e.g. 22.04]
• CPU Architecture: [e.g. x64 or M1]
• Local or Remote Debugging: [e.g, local]

Bug Description:
Please provide a clear and concise description of what happened.

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

1. Open...
2. Launch it...
3. Interact with it...
4. See error

Expected Behavior:
Please provide a clear and concise description of what you expected to happen.

Screenshots/Video Recording:
If applicable, please add screenshots/video recording here to help explain your problem.

Binary:
If applicable, please provide us with the binary to help us work with the issue faster.
This is especially helpful due to the dynamic nature of the debugger.
Here are a few options:

• Upload it privately using the Binary Ninja Portal file uploader and add the provided reference phrase here
• Directly attach it to this issue in a ZIP archive
• Share a publicly accessible link to it (For malware samples, we do not have access to VirusTotal; Malshare is an option)
• Email it to binaryninja at vector35.com, or join our slack and share with us in private
• We understand sometimes it is not possible to share the binary -- sure, no worries, we can still work with it!
• If your issue is general and not related to a specific binary, then there is no need to attach the binary as well

Additional Information:
Please add any other context about the problem here.

The issue body is an unfilled bug-report template and names no files, tests, or entry points. Clarify what analysis must be blocked, how target execution triggers it, and what observable behavior defines completion before locating the relevant debugger subsystem.