Fix C++ clang-format violations

[lavrovvalera]

Important

Link the implementing PR to this issue by including Closes #<issue_number>
in the PR description or commit message.

What

Fix all C++ clang-format violations detected by the clang-format CI job introduced in PR #102.

To collect all violations, you can use

bazel build --keep_going --config=clang_format //score/... //examples/...`

Once the codebase is clean, remove the continue-on-error: true guard from the
C++ clang-format check job so it becomes a blocking CI gate.

Acceptance Criteria

• bazel build --keep_going --config=clang_format //score/... //examples/... reports zero first-party violations (no output from the filter step)
• Process / Formatting → C++ clang-format check CI job passes without violations in the uploaded artifact
• continue-on-error: true removed from the clang-format job in .github/workflows/format.yml

How

Identify affected files and apply the formatter:

bazel build --keep_going --config=clang_format //score/... //examples/... 2>&1 \
  | grep "clang-formatted" | grep "^$(pwd)" | cut -d: -f1 | sort -u \
  | xargs clang-format -i

References

• CI job tracking these violations: .github/workflows/format.yml (added in PR Refactor the CI workflows #102)

[thatguysumeetkumar-code]

Hi, I'd like to work on this issue.
Can I start with #103?

[lavrovvalera]

@thatguysumeetkumar-code
thank you for the initiative)

I would ask you to wait until the #18 will be merged
the review is there, I need jsut to catch somebody, who has the commiter rigthts.
It is a huge code change, and it will collapse with your possible changes

Also we need to wait, or base on #102 one, where the actual formatting job is introduced.