feat(allyes): Remove redundant filters from exception_list_sitl

[valbv]

Solved Problem

INS-drivers had errors and can't build.

Currently, INS-drivers buildability isn't checked when merging pull-requests.
After these changes b7c5ba1 it was stopped.

Because of this, build-errors in this code-base go unnoticed.

Solution

INS-drivers build fixed.
Clang-tidy errors fixed.
Code-style errors (astyle) fixed in the separate commits.

Build more targets in px4_sitl_allyes:
Exclude specific targets from build instead of redundant big filters COMMON and DRIVERS in Tools/kconfig/allyesconfig.py

Changelog Entry

For release notes:

Restore driver build coverage in px4_sitl_allyes (previously silently skipped)

[dakejahl]

Most of this looks good but I think in the case of the vectornav, it should just be excluded from clang-tidy and astyle. We don't want to force a change on their library.

[valbv]

If I disable clang-tidy checks for "libvnc" as all, the error: "Error: no checks enabled" occurs.
I left one memory leak check for it.

[mrpollo]

The allyes fix is exactly right. The bare COMMON/DRIVERS prefixes were silently eating every driver including UART-only ones, and the surgical exclusion list is the right shape. Restoring real CI coverage here also surfaced a backlog of legitimate driver fixes (vectornav missing brace, sbgecom short-read + leak, vtxtable open() mode, vertiq_io proper EINTR/EAGAIN handling) that were hiding behind that hole.

Rebase-merging this so the per-driver commits stay individually bisectable.

Thanks for picking this up and running it all the way through, @valbv.

[valbv]

Thank you guys!