Clarify MethodHandles usage in FieldAccessHelper

Added comments to explain that setAccessible is still required to bypass access checks when using MethodHandles for field access, providing more context on the security and compatibility considerations.

Author: anidotnet

nitrite/src/main/java/org/dizitart/no2/repository/FieldAccessHelper.java

@@ -82,6 +82,7 @@ private static Object getFieldValue(Field field, Object obj) throws IllegalAcces
         try {
             // Use MethodHandles.lookup().unreflect which is available since Android API 26
             // This is more secure than setAccessible but requires the field to be accessible
+            // while MethodHandles provide a more modern API, setAccessible is still required to bypass access checks.
             field.setAccessible(true);
             MethodHandles.Lookup lookup = MethodHandles.lookup();
             MethodHandle getter = lookup.unreflectGetter(field);
@@ -99,6 +100,7 @@ private static void setFieldValue(Field field, Object obj, Object value) throws
         try {
             // Use MethodHandles.lookup().unreflect which is available since Android API 26
             // This is more secure than direct setAccessible + set
+            // while MethodHandles provide a more modern API, setAccessible is still required to bypass access checks.
             field.setAccessible(true);
             MethodHandles.Lookup lookup = MethodHandles.lookup();
             MethodHandle setter = lookup.unreflectSetter(field);