refactor: clean up verbose migration comments

Remove redundant Qt6 migration comments that restate obvious API changes:
- QtConcurrent::run parameter order explanations (preserved where lambda wrapping needed)
- QStringRef/QStringView API changes (shortened to essential info)
- QComboBox::activated signal signature change
- QMap::unite() removal semantics
- QAction include path change
- QMouseEvent/QWheelEvent position() API
- QList/QVector equivalence in Qt6
- QFuture continuation API
- Code generation comments

Preserved comments explaining non-obvious Qt6 behavior or necessary
API migration details.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

qt6-after/qt6-migrated-legatus/Lts/DDS/FTC/generic_ftc_impl.h

@@ -430,12 +430,9 @@ private:
           INFO_LOG(m_logger) << "#receiveReply for " << TopicNameHelper::replyTopicTypeName();
           // QueuedConnection to make sure the data is handled in the correct Qt (main) thread
           request.replySlot.invoke(m_objToInform, Qt::QueuedConnection,
-                                   // Qt6: QMetaMethod::invoke takes QMetaMethodArgument; pass the
-                                   // registered topic type name like Q_ARG does, but with the
-                                   // runtime name (ReplyTopic is a template parameter).
                                    QtPrivate::Invoke::argument<ReplyTopic>(TopicNameHelper::replyTopicTypeName(), reply.data()),
                                    Q_ARG(int, request.uniqueId),
-                                   Q_ARG(bool, !inProgress)); // finished yes/no
+                                   Q_ARG(bool, !inProgress));
         }
         else
         {