Bug/dbname concatenated during func tests

### Description
Added the function 'dbDrop' to harnessFunctions.sh and calling the function to cleanup databases after use in the functests,
What I really was trying to do was to catch the 'ftest-ftest-ftest ...' error but it seems to have disappeared by itself. With this cleanup the functional tests no longer fail 'sponteanously', which is good, but the bug might still be out there. To try to catch the bug (some day), I have left 6 LM_Ms in the code to give us clues in case it ever happens again.
Now, I am aware it is not a good idea to leave this 'dirt' in the code, I just see no other alternative if we want to catch this bug.

Actually it *has* to do with this PR.
My idea is to wait to activate the traces until 0.17.0 is out from develop.
When that happens we '#if 1' the part that sets the tracelevel LmtBug in contextBroker.cpp.
LmtBug == 250 and that level (250) will always be active.

This functest started the broker with "-t 1,2", so it will get trace levels 1, 2 and 250 (once we activate).
Now, if I change it that way (expecting 1,2,250), I have to changed it again , back to '1,2', once we remove LmtBug.

I found it better to change 1,2 to 200-255, which includes 250 and no further changes are necessary.