Fix dummy behavior ball approach with side offset

[Flova]

Checklist

• Run colcon build
• Write documentation
• Test on your machine
• Test on the robot
• Create issues for future work
• Triage this PR and label it

[Copilot]

Pull Request Overview

This PR updates the ball goal calculation for the CLOSE ball target by incorporating a side offset into the angle computation.

• Recalculates the ball approach angle using an adjusted ball v-coordinate.
• Updates goal coordinate computations to apply the side offset.

Comments suppressed due to low confidence (2)

bitbots_behavior/bitbots_blackboard/bitbots_blackboard/capsules/pathfinding_capsule.py:185

• [nitpick] Consider renaming 'ball_v_from_kick_foot' to a more descriptive name such as 'adjusted_ball_v' to better reflect its purpose as the side-offset adjusted ball coordinate.

ball_v_from_kick_foot = ball_v + side_offset

bitbots_behavior/bitbots_blackboard/bitbots_blackboard/capsules/pathfinding_capsule.py:188

• The side_offset is applied both in the adjusted ball_v computation and again when calculating goal_v, which may result in an unintended double offset. Please verify whether the double application of side_offset is intentional or if one instance should be removed.

goal_v = ball_v - math.sin(angle) * distance + side_offset