repo wide : Name SDRangel-owned threads for debugging

Assign descriptive names to SDRangel threads so thread activity can be
identified when investigating multi-threaded behavior, including crashes,
leaks, and synchronization issues in debuggers and others tools.

Use compact names to fit platform thread-name limits (14 chars) while
retaining the component and thread role where possible.

Signed-off-by: Robin Getz <rgetz503@gmail.com>

plugins/samplesink/hackrfoutput/hackrfoutputthread.cpp

@@ -30,6 +30,7 @@ HackRFOutputThread::HackRFOutputThread(hackrf_device* dev, SampleSourceFifo* sam
 	m_log2Interp(0),
     m_fcPos(2)
 {
+    setObjectName("HackRFOutput");
     std::fill(m_buf, m_buf + 2*HACKRF_BLOCKSIZE, 0);
 }