fix: Fix calculation of AABB for ShapeHitboxes

[spydon]

Description

Tried to reproduce #1478 without luck.

Checklist

• The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
• I have read the Contributor Guide and followed the process outlined for submitting PRs.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation in docs and added dartdoc comments with ///.
• I have updated/added relevant examples in examples.

Breaking Change

• No, this is not a breaking change.

Related Issues

Closes #1478

[st-pasha]

What would be the reported set of intersection points in this case?

[spydon]

What would be the reported set of intersection points in this case?

In the bug report you mean? Both start and end seems to be called for every tick.

[st-pasha]

I mean, normally when 2 shapes collide, we compute their set of collision points. But here the two shapes overlap exactly, so I was wondering what's going to happen to that set (in theory there are infinite number of collision points now). A circle-on-circle overlap would be interesting too...

[spydon]

I mean, normally when 2 shapes collide, we compute their set of collision points. But here the two shapes overlap exactly, so I was wondering what's going to happen to that set (in theory there are infinite number of collision points now). A circle-on-circle overlap would be interesting too...

Aah, now I get what you mean, with polygon collisions that have lines that are on each other the intersections points will be formed by the line that is created by each overlap and the points will be the start, end and middle of that line.
For circles that are exactly on top of each other four intersection points with pi/2 angle between them will be reported.