merge develop to master for QUD linux release v1.0.6.6

[Shashank Arora (shasaror)]

Description

1. Extended support for Debian 13 ARM64 platform.
2. Automated removal of existing QUD Debian packages during QUD installation via QSC/QPM.
3. Automated removal of existing QUD Userspace Debian packages during QUD installation via QSC/QPM.
4. Improved QSC/QPM cli error reporting on terminal during QUD driver installation.
5. Fix build-deb.sh Hard Dependency Causing Debian Installer Failures (bugfix/hard-depends-fails-debian-installation: Fix build-deb.sh Hard Dependency Causing Debian Installer Failures #118)
6. Updated versioning and release notes for QUD Linux v1.0.6.6

Fixes #

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Hotfix (urgent fix targeted at a release/x.y branch)
• Refactor (no functional change)
• Performance improvement
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test-only change
• CI / build-pipeline change

How has this been tested?

Checklist

• All required CI checks are green on the latest commit of this PR
• Build succeeds following the steps in the README / src/linux/README.md
• My code follows the Code Style Guidelines of this project
• My branch follows the naming convention: <branch-prefix>/<area>/<description>
• PR title follows the Conventional Commits format with our full-word types (feature / bugfix / hotfix / docs)
• I have performed a self-review of my own code
• I have added code comments in areas that are complex or hard to understand
• My changes generate no new compiler warnings
• I have added tests for my fix or feature (or noted why tests are not feasible)
• New and existing tests pass locally with my changes
• My branch is rebased onto the latest develop (or release/x.y for hotfix) - no merge commits
• Every commit has Signed-off-by: (DCO) - see CONTRIBUTING.md
• I have linked the relevant issue if any (Fixes #...)
• Any dependent changes have been merged and published in downstream modules