Fix static deinitialization fiasco in destructor

[AngryLoki]

aql_profile.cpp defines:

Logger::mutex_t Logger::mutex_;

DESTRUCTOR_API void destructor() {
  Logger::Destroy();
  Pm4Factory::Destroy();
}

logger.h

  static void Destroy() {
    std::lock_guard<mutex_t> lck(mutex_);  // <--------------------- fails here
    if (instance_ != NULL) delete instance_;
    instance_ = NULL;
  }

There is no guarantees for destruction order, but in my case __attribute__((destructor)) runs after C++ destructors for static objects, trying to lock destroyed mutex.

To fix the deinitialization order, this PR removes custom destructor and replaces it with modern "Construct on First Use" idiom (a.k.a. Meyers' singletons).

Closes #4

[AngryLoki]

(rebased)

[jayhawk-commits]

Imported to ROCm/rocm-systems