fix: correctly offset vector input

[camsjams]

Aside from fixing the issue, to get there I had to write some tests and iron out the exact nuances. The final result looks simpler overall, but there were some fun bugs to kill as I changed the Vec data code.

I've added a lot of unit tests in different places as a result.

Issue

The pointer of the Vector data was wrong, caused by a bug when the index of the first vector param was not zero.

Solution

By always starting with the base offset, the bug is fixed.

These lines were the culprit, as this would only run if the first vector was also the first input:

if (byteIndex === 0 && byteIndex === paramIndex) {
  return baseVectorOffset;
}

Fixes #881

Note: I'd recommend also seeing the original PR here: #497 which includes a still accurate diagram.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	95.05%	4643/4885
🟢	Branches	83.89% (-0.03% 🔻)	823/981
🟢	Functions	92.32%	890/964
🟢	Lines	95.07%	4440/4670

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / utilities.ts	100%	87.5% (-2.5% 🔻)	100%	100%

Test suite run success

794 tests passing in 115 suites.

Report generated by 🧪jest coverage report action from 80f9cc5

[Dhaiwat10]

Finally 😅