Use QML_ELEMENT & QML_SINGLETON for registering

[HTRamsey]

This compiles cpp code into QML for singletons

[Copilot]

Pull Request Overview

This PR modernizes QML type registration by migrating from manual qmlRegisterSingletonType calls to the declarative QML_ELEMENT and QML_SINGLETON macros for C++ types exposed to QML. The changes improve type safety and follow Qt 6's recommended registration patterns.

• Replaces manual singleton factory functions with declarative QML macros
• Updates QML import statements to use newly registered singleton types
• Modernizes the build system with proper QML module configuration

Reviewed Changes

Copilot reviewed 26 out of 26 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/Utilities/Shape/ShapeFileHelper.h	Adds QML_ELEMENT and QML_SINGLETON macros for QML integration
src/QmlControls/ScreenToolsController.h	Uncomments QML_ELEMENT and QML_SINGLETON macros
src/QmlControls/QGroundControlQmlGlobal.h	Adds QML_NAMED_ELEMENT and QML_SINGLETON macros
src/MAVLink/QGCMAVLink.h	Adds QML_NAMED_ELEMENT and QML_SINGLETON macros
src/AnalyzeView/LogDownloadController.h	Uncomments QML_ELEMENT and QML_SINGLETON macros
Multiple QML files	Removes now-unnecessary import statements for singleton types
src/QGCApplication.cc & src/QmlControls/QGroundControlQmlGlobal.cc	Removes manual singleton factory functions and registration calls
CMakeLists.txt & src/CMakeLists.txt	Adds QML module configuration

[Copilot]

The logging category 'MAVLinkMessageLog' is used but may not be defined. The commented line above suggests this should use 'LogDownloadControllerLog' category instead.

[Copilot]

The logging category 'MAVLinkMessageLog' is used but may not be defined. This appears to be inconsistent with the original logging approach.