Print library path in the initialization message

This is useful when chainloading, since it now tells you where eactly
it's loading the library from.

CHANGELOG.md

@@ -43,6 +43,9 @@ Versioning](https://semver.org/spec/v2.0.0.html).
   instead of immediately terminating the process. An annoying desktop
   notification will still be shown every time you load a plugin until you fix
   this.
+- Yabridge now prints the path to the `libyabridge-{vst2,vst3}.so` library
+  that's being used on startup. This tells you where the chainloader is loading
+  the library file from. Because you can never have too much information, right?
 - `effProcessEvents` VST2 calls are now filtered out from the log when
   `YABRIDGE_DEBUG_LEVEL` is set to 1.
 

src/plugin/bridges/common.h

@@ -26,6 +26,7 @@
 #include <version.h>
 
 #include "../../common/configuration.h"
+#include "../../common/linking.h"
 #include "../../common/notifications.h"
 #include "../../common/utils.h"
 #include "../host-process.h"
@@ -142,7 +143,8 @@ class PluginBridge {
                  << " (32-bit build)"
 #endif
                  << std::endl;
-        // TODO: Show this library's path now that we're chainloading
+        init_msg << "library:       '" << get_this_file_location().string()
+                 << "'" << std::endl;
         init_msg << "host:          '" << plugin_host_->path().string() << "'"
                  << std::endl;
         init_msg << "plugin:        '" << info_.windows_plugin_path_.string()