feat: add two half pass approach to beam potential

[davidrudlstorfer]

FYI: test pipeline does not fail because we do not write out the file during testing (the validation happens during the write), but the pre-commit hook where we verify the input file fails

Follows 4C-multiphysics/4C#1957

[Copilot]

Pull request overview

Adds support for 4C’s “two half pass” approach configuration to BeamMe’s beam potential input generation, aligning generated YAML with upstream 4C expectations (per referenced 4C PR).

Changes:

• Extend BeamPotential.create_header() to include a two_half_pass option and emit it into the beam_potential header dict.
• Update the beam potential integration test to pass two_half_pass=True.
• Update the corresponding reference YAML file to include two_half_pass: true.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/beamme/four_c/beam_potential.py	Adds two_half_pass argument + writes it into the generated beam_potential header.
tests/integration/test_integration_four_c_beam_potential.py	Passes two_half_pass=True when constructing the beam potential header in the integration test.
tests/reference-files/test_integration_four_c_beam_potential_helix.4C.yaml	Updates expected YAML output to include two_half_pass: true.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[davidrudlstorfer]

pipeline now succeeds because the changes are in fourcipp