Use <lttng/lttng.h> in lttngpy and clean up includes

[reeceholland]

Description

This PR updates lttngpy to use the recommended umbrella LTTng header:

#include <lttng/lttng.h>

instead of including individual LTTng headers (domain.h, event.h, lttng-error.h, etc.).

Changes:

• Replace groups of LTTng includes in lttngpy .cpp files with <lttng/lttng.h>.
• Clean up redundant includes in corresponding .cpp files.
• Fix uncrustify style in snapshot.cpp so lttngpy tests pass.

No functional behavior changes are intended; this is an include/style cleanup.

Fixes #220

Is this user-facing behavior change?

Did you use Generative AI?

Additional Information

[christophebedard]

Thanks for the PR! I just have some minor comments.

[reeceholland]

Updated per review: added <lttng/lttng.h> to all lttng-ctl users, fixed include ordering, and kept the formatting commit separate. Thanks!

[christophebedard]

Looks good, thank you again for the PR and thank you for iterating with me! I'll trigger CI.

[christophebedard]

Pulls: #222
Gist: https://gist.githubusercontent.com/christophebedard/a5ff813ad055e225f9ac8b2e7dcd298b/raw/6d81537d1e9c35b6951628b23dc65930868b3335/ros2.repos
BUILD args: --packages-above-and-dependencies lttngpy
TEST args: --packages-above lttngpy
ROS Distro: rolling
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/18022

• Linux
• Linux-aarch64
• Linux-rhel
• Windows

[christophebedard]

@Mergifyio backport kilted jazzy

[mergify]

backport kilted jazzy

✅ Backports have been created

Details

• #231 Use <lttng/lttng.h> in lttngpy and clean up includes (backport #222) has been created for branch kilted but encountered conflicts

Cherry-pick of 91ff616 has failed:

On branch mergify/bp/kilted/pr-222
Your branch is up to date with 'origin/kilted'.

You are currently cherry-picking commit 91ff616.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   lttngpy/src/lttngpy/channel.cpp
	modified:   lttngpy/src/lttngpy/channel.hpp
	modified:   lttngpy/src/lttngpy/context_app.cpp
	modified:   lttngpy/src/lttngpy/context_lttng.cpp
	modified:   lttngpy/src/lttngpy/context_lttng.hpp
	modified:   lttngpy/src/lttngpy/context_perf.cpp
	modified:   lttngpy/src/lttngpy/context_perf.hpp
	modified:   lttngpy/src/lttngpy/event.cpp
	modified:   lttngpy/src/lttngpy/event.hpp
	modified:   lttngpy/src/lttngpy/session.cpp

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   lttngpy/src/lttngpy/snapshot.cpp

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

• #232 Use <lttng/lttng.h> in lttngpy and clean up includes (backport #222) has been created for branch jazzy but encountered conflicts

Cherry-pick of 91ff616 has failed:

On branch mergify/bp/jazzy/pr-222
Your branch is up to date with 'origin/jazzy'.

You are currently cherry-picking commit 91ff616.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   lttngpy/src/lttngpy/channel.cpp
	modified:   lttngpy/src/lttngpy/channel.hpp
	modified:   lttngpy/src/lttngpy/context_app.cpp
	modified:   lttngpy/src/lttngpy/context_lttng.cpp
	modified:   lttngpy/src/lttngpy/context_lttng.hpp
	modified:   lttngpy/src/lttngpy/context_perf.cpp
	modified:   lttngpy/src/lttngpy/context_perf.hpp
	modified:   lttngpy/src/lttngpy/event.cpp
	modified:   lttngpy/src/lttngpy/event.hpp
	modified:   lttngpy/src/lttngpy/session.cpp

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   lttngpy/src/lttngpy/snapshot.cpp

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally