Fixed out of bounds string access found by ASan

Check length of offset before taking adrees of a range like `&string[n - 8]`.

Looked for similar cases and also reordered another case to check length first, may or may not have been a problem, but safer this way.

ASan would catch this *during* VTK builds, while generating the wrappings.

(cherry picked from commit ccbda30c)

Wrapping/Tools/vtkParseMethodType.c

@@ -105,7 +105,7 @@ int vtkParseMethodType_IsAsStringMethod(const char* name)
   if (vtkParseMethodType_IsGetMethod(name))
   {
     n = strlen(name);
-    if (!strncmp(&name[n - 8], "AsString", 8))
+    if (n > 8 && !strncmp(&name[n - 8], "AsString", 8))
     {
       return 1;
     }
@@ -133,7 +133,7 @@ int vtkParseMethodType_IsRemoveAllMethod(const char* name)
   if (vtkParseMethodType_IsRemoveMethod(name))
   {
     n = strlen(name);
-    return (!strncmp(&name[6], "All", 3) && (n > 9) && isupper(name[9]));
+    return (n > 9) && isupper(name[9]) && !strncmp(&name[6], "All", 3);
   }
 
   return 0;

Wrapping/Tools/vtkParseProperties.c

@@ -142,7 +142,7 @@ static int isAsStringMethod(const char* name)
   if (isGetMethod(name))
   {
     n = strlen(name);
-    if (!strncmp(&name[n - 8], "AsString", 8))
+    if (n > 8 && !strncmp(&name[n - 8], "AsString", 8))
     {
       return 1;
     }