Fix segmentation fault due to varargs on Apple M1

[thierry-martinez]

Calling conventions on Apple M1 seem to differ for varargs: the program below prints "The answer is " on M1 while it prints "The answer is 42" on Linux.

void f(int something, int answer) {
  printf("The answer is %d\n", answer);
}

int
main(int argc, char *argv[])
{
  void (*ptr)(int, ...) = (void *) f;
  ptr(18, 42);
}

This commit fixes all type annotations for functions that are extracted from ap_manager_t*. This solves segmentation faults observed when apron is compiled on Apple M1.

Another solution would have been to use the type void (*ptr)(), but expliciting types look like a safer approach. Types allow us to find and fix the following suspicious line (apron/ap_generic.c, line 167):

    res = destructive ? abs : copy(abs);

whereas copy is AP_FUNID_COPY of type void* (*copy)(ap_manager_t*,void*) (the argument man was obviously missing).

[antoinemine]

Thank you very much, the patch looks good. Thank you also for catching the erroneous call to copy.