Isolate tmp CTS APK directories

Many of our CTS test modules, before running any tests, deploy
temporary APK files to specific-per-test-module directories on
the device:

    /data/local/tmp/cts/permissions/
    /data/local/tmp/cts/permissionmultiuser/
    /data/local/tmp/cts/permission2/
    /data/local/tmp/cts/permissionui/
    /data/local/tmp/cts/role/
    /data/local/tmp/permissioncontroller/tests/inprocess/
    /data/local/tmp/permissioncontroller/tests/permissionui/

But, we've run into cases where a parent directory shared by multiple
tests (e.g., /data/local/tmp/cts) is created by test module A, but for
whatever reason, test module B does not have access to its filesystem
permissions, resulting in difficult-to-diagnose "Test Module Error"s.

The solution here is to only use /data/local/tmp as the shared parent
directory, which all test modules should have access to.

So we instead have:

    /data/local/tmp/cts-permission/
    /data/local/tmp/cts-permissionmultiuser/
    /data/local/tmp/cts-permissionpolicy/
    /data/local/tmp/cts-permissionui/
    /data/local/tmp/cts-role/
    /data/local/tmp/pc-inprocess/
    /data/local/tmp/pc-permissionui/

This avoids the possibility of /data/local/tmp/cts or
/data/local/tmp/permissioncontroller being locked out due
to conflicting fileystem permissions between test module runs.

Fix: 295966565
Test: Run :alltests both locally and in ABTD
Change-Id: Icfd2e0e5f09ada03246ebc9cac0f609e17b01baf