Add GPU-accelerated particle system for vector field visualization

[Copilot]

• Understand repository structure and build system
• Design particle system architecture
  • Create compute shaders for particle seeding
  • Create compute shaders for particle advection (integrate through vector field)
  • Create compute shaders for particle lifetime management
  • Create rendering shaders for particle trails with fade-out
• Implement particle system component
  • Create particlesystem.cpp in src/components/particlesystem/
  • Implement event handler registration
  • Implement GPU buffer management (particle positions, velocities, lifetimes, trails)
  • Implement compute shader dispatching
  • Implement rendering logic
• Add particle system to CMakeLists.txt
• Add particle system shaders to CMakeLists.txt
• Create UI for particle system controls
• Hook up particle system to application
• Add example hook for binding volume textures to particle system
• Address code review feedback
• Successfully build and integrate into viamd
• Remove CodeQL build artifacts (unintentionally added)

Changes in this commit

Removed all _codeql_build_dir/ contents and _codeql_detected_source_root symlink that were unintentionally committed. Added these patterns to .gitignore to prevent future accidental commits of CodeQL build artifacts.

Original prompt

I would like you to implement a new component in viamd called particlesystem which simulates particles in vector fields. The input format for the particle system are volumes with 4 components, encoding a gradient in xyz and the scalar value in w. The particle system should use compute shader(s?) to seed, advect and handle lifetimes of particles. The seeding strategy for the first iteration can be based on randomly placing points within the regions where the scalar value is within a certain range.
For rendering, since the vector field is static, I'm thinking of having particles with trails that fade out its opacity to provide a hint of where they came from.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[scanberg]

@copilot
I want you to prune and remove everything which has to do with codeql that you introduced into this PR. I have no idea why you bloated this PR with that?

[Copilot]

@copilot
I want you to prune and remove everything which has to do with codeql that you introduced into this PR. I have no idea why you bloated this PR with that?

Removed all CodeQL build artifacts from the PR in commit 6ae828b. The _codeql_build_dir/ directory and symlink have been deleted and added to .gitignore to prevent future accidental commits. The build still works correctly.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)