add coverage configuration file
switch particle_manager to 2 types of data_manger

first step in refactoring things so that eneventually, the data for
particles will be handled by two different classes: (i) one using
*primarily* python's internal interface and (ii) one using input
files (FILE-IO)
use only input file to control lammps

work is focussed on using input files (FILE-IO). Using
the internal interace has been removed and will be added
later.  Now, using the lammps executable (through LammpsProcess)
instead of the python interace.  Also reworked flow_pois.py example
to ensure that the results match using the in.flow.pois script.
make lammps executable on travis-ci
add support of uuids.

now we use the uuid in simphony and keep a map from that uuid to
the id that lammps uses.
add dummy-config class and improve data manager

add dummy configuration into seperate module.  also
improve data manager so that it has seperate particlecontainers
and handles deletion of particles