AArch64: Use front end query when allocating VI Thunks

[Akira1Saitoh]

This commit updates TR::ARM64CallSnippet::generateVIThunk to use front end query to determine the type of memory where VI thunk instructions are stored.

[knn-k]

Jenkins test sanity alinux64,amac jdk17

[knn-k]

p uses compileRelocatableCode() while z uses storeOffsetToArgumentsInVirtualIndirectThunks() in generateVIThunk(). The z code was changed by PR #6910:

openj9/runtime/compiler/p/codegen/CallSnippet.cpp

Lines 973 to 976 in dca494d

	if (comp->compileRelocatableCode())
	thunk = (uint8_t *)comp->trMemory()->allocateMemory(codeSize, heapAlloc);
	else
	thunk = (uint8_t *)cg->allocateCodeMemory(codeSize, true, false);

openj9/runtime/compiler/z/codegen/S390J9CallSnippet.cpp

Lines 55 to 58 in dca494d

	if (fej9->storeOffsetToArgumentsInVirtualIndirectThunks())
	thunk = (uint8_t *)comp->trMemory()->allocateMemory(codeSize, heapAlloc);
	else
	thunk = (uint8_t *)cg->allocateCodeMemory(codeSize, true);