Port MASTG-TEST-0082 (by @appknox)

[jeel38]

closes #3010

[cpholguera]

Prefer to use the technique instead of specific tools in TESTS

https://mas.owasp.org/MASTG/techniques/ios/MASTG-TECH-0111/

Also, let's do the evaluation (check for true, in this case) later.

Suggested change

	1. Run a static analysis using @MASTG-TOOL-0111 to extract entitlements from the binary to check the value of the `get-task-allow` key and is set to `true`.
	1. Use @MASTG-TECH-0111 to extract entitlements from the binary and obtain the value of the `get-task-allow` key.

[cpholguera]

The static analysis step should be enough. However, you still can refer to this TECH. See overview

[cpholguera]

Suggested change

	The entitlement get-task-allow is false, and anti-reverse engineering measures prevent debugger attachment attempts.
	The output contains the value of the `get-task-allow` entitlement.

[cpholguera]

Suggested change

	The test fails as the entitlement get-task-allow is true, allowing debugger attachment.
	The test fails if the `get-task-allow` entitlement is `true`.

[cpholguera]

Suggested change

	The test evaluates whether an iOS application is configured to allow debugging. If an app is debuggable, attackers can leverage debugging tools to reverse-engineer the application, analyse its runtime behaviour, and potentially compromise sensitive data or functionality.
	The test evaluates whether an iOS application is configured to allow debugging. If an app is debuggable, attackers can leverage debugging tools (see @MASTG-TECH-0084) to analyse the runtime behaviour of the app, and potentially compromise sensitive data or functionality.

[cpholguera]

First round of review done. Please remember to include a demo using https://github.com/cpholguera/MASTestApp-iOS

Thanks a lot @jeel38!