removing maximum size and amount of log files
changed log file name
using slice-file library to retrieve log lines

- using library ‘slice-file’ to get the last lines of the files
efficiently.
- changed log file name
added slice-file library as a dependency
watching log files instead of retrieving it again

instead of retrieving the end of each file to send the last lines on
response, now we keep track of the last lines on memory. we get the
last lines once, than we watch for changes on file and add new lines to
memory, removing old ones. keeping always the most recent ones.
lastStatus also informs the amount of repeatitions

- ‘lastStatus’ is now an object with two paramaters. ‘label’ is what
‘lastStatus’ used to be, the identification of the situation/case that
happened in the last request. ‘counter’ holds how many times the same
‘label’ has been repeated.
- the guards of each log message is now executed inside the function
‘loggingOnGuards(logLevel, logMessage, label, sendLastStatus)’.
- we send ‘lastStatus’ object inside a message object to the parent
thread (server.js) in the end of every request processed by us. bet it
an error, a bad response and, of course, on good responses.
added route to both logs

- added route ‘/log’ that sends back both logs on the same text.
- as we now receive messages from out child thread that may contain
only ‘lastStatus’, I have added checks on the other attributes of the
message. If they are defined, get their values, if not, keep the old
values.
- we now get the amount of last lines to retrieve from log file, from
our JSON configuration file
adde 'numberOfLastLogLines' to JSON config file

we now get the amount of last lines to retrieve from log file, from our
JSON configuration file. I’ve set it to 40.
Merge branch 'node.js-dataGrabber'