EEP handling cleanup

This is my first try to separate devices and EEP messages.
If we would like to support sending messages, we must first be able to generate them. And so we need to extract message handling from the devices.
IMHO this improve readability and it should be simpler to implement new EEPs (first 4BS).

I used the "Light temperature and occupancy sensor" to demonstrate the separation.

Could you please have a look at:
src/main/java/org/opencean/core/eep/LightTempertureAndOccupancySensor.java
src/main/java/org/opencean/core/packets/data/PacketDataEEPA50802.java

So, if this seems to be good for you, we could handle EEP entries (set of range_min, range_max, ...) more generic. But first I would like to know, if this violates your architecture.
Perhaps we have to do some rework who is responsible for the data.
I do not use an exception here, because I thought, it could be ok.
Perhaps the caller decided to write just the last x bits of a value and it is ok for the caller to ignore the upper bits.
So I wanted just signal, if all was inserted or not (not signal a failure).