Fix client name and tags handling

[eXpl0it3r]

Something I knew a long time ago, but had never really hard evidence for it, started to wreck havock in certain circumstances, because the UpdateSettings method can be called in parallel. As such, you need to ensure that changes to the underlying cache values as well as reading from them, is properly handled, otherwise you run into "fun" race conditions and crashes.

This fixes #48

Additionally, I realized that the client name and tag filtering was done in a wrong way, thus not actually getting applied.

Included fixes / changes:

• Change detection for settings has been fixed through deep cloning
• Tags comparison logic has been fixed to properly filter by tags
• Client data is fetched at the correct time now (before the project)
• Client data is localized as it's just a dependency for the project query
• All public methods of the ClockifyService are protected by a semaphore to prevent threading issues
• Title formatting is now case insensitive (e.g. {projectName} or {ProjectName} or {projectname})