Do not enable calibration by default, so people get to see the warnings about codelets still not being calibrated

- create config files to store definitions
 - include/chameleon_config.h: definitions exposed to the public (installed file)
 - control/config.h: additional definitions used internally
- modify source code to call the config files when it is necessary (when the different "if defined" are used)

    - use (starpu_cpu_func_t) 1 trick, same as cuda_func
    - cpu funtions are not defined anymore avoiding the dependency to coreblas
    - add #if !defined(CHAMELEON_SIMULATION) where it is needed
    - remove dependency to the coreblas library (become useless)
    - remove useless simucblas, simulapacke libraries
    - remove CHAMELEON_SIMULATION_MAGMA cmake variable and definition
      - keep using CHAMELEON_USE_CUDA and CHAMELEON_USE_MAGMA to consider CUDA kernels
      - this avoid to introduce useless new variables
    - work on messages

don't force calibration in simulation mode. It does not make sense, and hides the StarPU detailed warning about missing calibration

to change the default values for tag_width(=31) and tag_sep(=24).
Today, it serves only with starPU.

MPI tag upper bound: MPI_TAG_UB is included (so on most platform the default values tag_width=31, tag_sep=24 are ok)

To use your own progress indicator,
- Define a function with prototype "void my_update_progress(int currentValue, int maximumValue)"
- Pass it to chameleon with "ierr=MORSE_Set_update_progress_callback(my_update_progress)"
- Activate progress indicator with MORSE_Enable(MORSE_PROGRESS)

IT is OFF by default
It is activated with MORSE_Enable(MORSE_PROGRESS)
In the timing routines, it is activated with --progress
No progress is printed for tasks faster than 10 seconds

chameleon: add a out_of_core example, requires to handle the case where starpu handles itself the allocation of tiles -> we give a NULL pointer through the get_blkaddr function for registering

Fix a large bunch of warnings, and there are still mistakes that should be fixed before the SC release

Fix build with starpu1.1 which doesn't have starpu_mpi_comm_{rank,size}: let's just call RUNTIME_comm_{rank,size} which already do things properly