Add DynamicConfig support for CtsHiddenApiBlocklistApiTestCases

As all the hidden API tests verify the accessibility of the same set of
APIs if an API that was previously inaccessible becomes accessible then
it would likely break all the tests. Therefore, this change adds one
set of dynamic config called CtsHiddenApiBlocklistApiTestCases.dynamic
and uses it for all the CtsHiddenApiBlocklist*TestCases.

Due to limitations in the build only one of the tests that use it can
reference the file in the 'data' property. That test is
CtsHiddenApiBlocklistCurrentApiTestCases. However, as all of the tests
use it from the same location it still works. The only issue is that
changes to the file will only have an effect when the
CtsHiddenApiBlocklistCurrentApiTestCases test is built.

Although all the tests use the same data this change follows the same
pattern as the SignatureTest of having the name of the dynamic config
provided by an instrumentation-arg so that a future refactoring can
move the handling of the DynamicConfig into the AbstractApiTest class.

Bug: 204723907
Test: atest CtsHiddenApiBlocklistApi27TestCases \
            CtsHiddenApiBlocklistApi28TestCases \
            CtsHiddenApiBlocklistCurrentApiTestCases \
            CtsHiddenApiBlocklistTestApiTestCases \
            CtsHiddenApiBlocklistDebugClassTestCases
Merged-In: I058a282b6020883cc2851c6516042446ae932d59
Change-Id: I058a282b6020883cc2851c6516042446ae932d59
(cherry picked from commit b51e76ab172d975a5b30e973581541d8dfb3f3ed)