Use array element type not basic type for primitive array access

[rootvector2]

InstConstraintVisitor checks the primitive array load/store instructions with ArrayType.getBasicType(), which returns the innermost basic type and drops the dimension count, so iaload/iastore (and the long/float/double/short variants) applied directly to a multidimensional primitive array such as int[][] pass Pass3b even though the component type is int[], a reference. The reference/byte/char siblings (aaload/aastore, baload/bastore, castore) already use getElementType(); this switches the ten primitive *aload/*astore checks to match. For a one-dimensional array getElementType() returns the same object as getBasicType(), so valid code verifies exactly as before. Found while auditing the *ALOAD/*ASTORE element-type checks against ArrayType.

• Read the contribution guidelines for this project.
• Read the ASF Generative Tooling Guidance if you use Artificial Intelligence (AI).
• I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute?
• Run a successful build using the default Maven goal with mvn; that's mvn on the command line by itself.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body.