useProximity throws error on getCoords

[jweinstein92]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

Current behavior

When using useProximity when a node is dragged, a console error is thrown

Expected behavior

There should be no error thrown when dragging a node

Minimal reproduction of the problem with instructions

• visit the useProximity storybook demo https://reaflow.dev/?path=/story/demos-proximity--simple
• Open chrome dev console
• begin dragging a node
• notice the error Cannot read properties of undefined (reading '0') which stems from useProximity's getCoords call

The getCoords definition expects the call to include a layoutXY property like in useNodeDrag

What is the motivation / use case for changing the behavior?

Correct usage of the getCoords function

Environment

Libs:
- react version: 18.2.0
- reaflow version: 5.1.1


Browser:
- [x] Chrome (desktop) version 108.0.5359.124
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: XX  
- Platform:  

Others: