Fixed unecessary axes array reallocation in GamePad update - Issue (#…

[kartik815]

Optimize Receiving Objects Step to Reduce Initialization Delay (#842)

Description

This PR addresses issue #842 by improving the performance of the receiving objects step in the engine.
It reduces the delay when processing incoming objects, ensuring smoother initialization and better overall responsiveness.

Fixes #842

Checklist

• I have read the contributing guidelines
• My code follows the project's coding standards
• This PR focuses on a single change

[mvaligursky]

Thanks for the PR! A few things to address before this can land:

1. Correctness regression in the axes copy (blocker). The new code resizes axes before snapshotting it into previousAxes. If gamepad.axes.length ever differs from the previous axes.length, previousAxes ends up with undefineds (when growing) or silently drops tail values (when shrinking). Please snapshot axes → previousAxes using the old length first, then resize and copy gamepad.axes → axes.

2. Style / lint. for(let → for (let, add spaces around <, use the cached-length idiom (for (let i = 0, l = arr.length; i < l; i++)) like the rest of the file, drop the double blank line, and reword the misleading // resizing array if size changed comment (the resize is unconditional). npm run lint will flag some of these.

3. PR title/description look copy-pasted from a different template and don't describe what this PR actually does. Please update them to cover the gamepad axes change and also mention the unrelated buttons[i] → buttons[j] fix in get previous() so it isn't missed.