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.
No, don't get me wrong. The method with the 3 blocks separated by the empty lines just looks as if there are in fact three test methods in one. I agree with you in having 20 test methods would absolutely overkill.
And I must admit that I didn't check if there are indeed 3 different cases checked :-). 
Anyway it would be hard for me to find out from the JUnit Exception what the real problem was if one of the asserts would fail.