Ignoring mobsf rule triggering false positives

[critt]

mobsf is now configured to ignore the following two checks:

• android_manifest_usescleartext
  • this check fails and has valid output. I am using this flag for convenience, as it makes it a lot easier currently to work with both local and cloud backend environments. I have raised an issue to document this: App permits all cleartext traffic #13
• android_task_hijacking1
  • this rule triggers a false positive. see mobsf false positive #11