[Android] Adds guardrails for non apk fuzzing

[IvanBM18]

Overview

In a previous stack of PRs (See #5453) I made a ton of changes for improving android fuzzing overall error detection when executing test cases, but, as i got pointed out, my changes assumed that android fuzzing work exclusively under apks, so some of the checks/validations didn't take into account jobs where no APK nor PKG_NAME is provided.

This PR focus on tuning various checks/validations previously altered in the stack of Prs above, so that if in android fuzzing with a binary(with this i mean non-apk fuzzing) then we go back to the usual checks that we had in place.

Changes

• Bad build check in tescase_manager.py now only checks for an apk process liveness if an apk package is found.
• The test cases directory in app.py defaults to the old (non accesible by apks) dir if no apk is found.
• When clearing the directory in device.py we now clean using the find command, as my previous command could ignore the hidden files(e.g: .<filename>)
• Exit info is only checked if fuzzing with an apk, else we ignore this

Tests

• Introduces a ton of unit tests for the non apk test cases
  Fuzzing is correctly executed on valid APKS:

And it continues to fail on invalid apks.

[dylanjew]

LGTM