Ensure all package loads in setUpClass() take place inside a transaction

[jacobtylerwalls]

#10711 works toward isolating the package loads necessary for test cases, but there were a handful of package loads that couldn't fully be moved after super().setUpClass() initiates a transaction (so that they roll back cleanly when the class is torn down).

arches/tests/views/api_tests.py

Lines 41 to 44 in 350e4a7

	if not models.GraphModel.objects.filter(pk=cls.data_type_graphid).exists():
	# TODO: pull this up higher so that it's not depending on running outside a transaction
	# same issue in command_line_tests.py
	test_pkg_path = os.path.join(test_settings.TEST_ROOT, "fixtures", "testing_prj", "testing_prj", "pkg")

This can cause annoying red herring test failures if the package load fails for unrelated reasons as experienced in #9613 (comment).

We should identify the root cause and fix the setup (or adjust the failing tests).

[jacobtylerwalls]

• permission_tests
• api_tests
• command_line_tests
• resource_tests