Fixes/calloc

[ivanazuzic]

This should fix #135:

• The created Blobs keep track of their creator (so-called origin, which can be either Calloc or Malloc)
• The idea is to know that the Blob created by calloc, which has a value Bot is actually supposed to be 0, because calloc zero-initializes the allocated place
• The type argument was returned to the signature of the update_offset function from the value domain because it's necessary to know the type of the zero which is produced by calloc
• Calloc used to take only one argument n * size and now those two are separated so calloc takes n and size
• Tests for calloc have been added
• Type was added as parameter to the eval _offset function of the value domain to make possible to read 0 when something was allocated by calloc and is not initialized yet
• Functions bot_value, init_vaue and top_value have been moved from base analysis to valueDomain. There a top_value function already existed and now, not to keep two top_value functions, a combination is kept in the valueDomain only (it resembles more to the one from the base analysis, which was more specific about arrays). The functions is_mutex_type and is_immediate_type have been moved together because they were only used by the functions that now went to the value domain.
• Partition arrays parameter has been added to the calloc tests.