Unload problematic modules automatically (PulseAudio) & Improve Multi-Threading

[Curve]

This PR implements some changes on how we handle problematic modules proposed by @D3SOX.

The Problem

Currently we only detect if the switch-on-connect module is loaded and if so we prompt the user to unload it.
However the module role-cork is also causing problems.
Adding a detection for that modules would require us to show the user yet another prompt.

This may impact users differently:

• Users without much knowledge
  • May be intimidated by a big red prompt telling them they have to unload the module
• Users that don't want to permanently disable the module / Users that don't know how to _{^{(in case they didn't read our wiki entry regarding this issue)}}
  • Always have to click through the prompts on start up and are required to reload the modules themselves after soundux exits

Proposed Solution

Our proposed solution is to automatically unload those modules from soundux and reload them once soundux exits.
That way the user is not required to click through dozens of prompts to use the application and continue to make use of the problematic modules after soundux exits.

Possible Improvements

• Notify the user about what we do, in form of a prompt in the frontend (@D3SOX ?) - So that the user doesn't experience problems without knowing where they come from (in this case they may be caused because we unloaded some modules)

[Curve]

I just pushed another change that greatly improves Mutli-Threading, however it's not yet fully complete.

The Problem

The program would often dead-lock and the mutex-code was really messy.

Proposed Solution

• Update lockpp to make mutex-access more explicit.
• Make PlayingSound hold and control it's own mutexes (This was previously done by gAudio), that way we greatly improve the messy code
• Rethink the Multi-Threading

Further (required) improvements

• Adjust Windows Code to new changes
• Adjust gData to new changes