#16 created ForceArrayCritical annotation to prevent copies of array

[vincent-grosbois]

• When this annotation is added to a method or a class, then all
  wrapper calls will use Get/ReleasePrimitiveArrayCritical pair instead
  of Get/ReleaseArrayElements pair.

[saudet]

Thanks! Let's also create a small test to make sure it works.

[saudet]

Also let's make it behave like @NoException, unless you see a good reason not to?

[saudet]

Hum, there's no test for @NoException, I'm just relying on the presets build to test that at the moment, so let's not worry about a test for the critical one either.

Anyway, as per the JDK's documentation, this function isn't about arrays, it basically stops the JVM:
https://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/functions.html#GetPrimitiveArrayCritical_ReleasePrimitiveArrayCritical
Since this is really about the method itself and not about each argument a name like @CriticalRegion would reflect that better. It will also allow us to use transparently other available JNI functions such as GetStringCritical() and potentially others as they show up for other kinds of objects or for other purposes that also require a stopped JVM.

For this reason, it basically has the same semantics as @NoException, but instead of dealing with C++ exceptions, it enables a critical region in the JVM.

[vincent-grosbois]

Hi @saudet
I've updated my commit, hopefully it updates the PR as well.
I made it behave like NoException annotation, so that it will recursively look for the tag in parent classes.
Also renamed the annotation.