feat: Add translateByVector2 method to Matrix4

[luanpotter]

Before the deprecation of the dynamic translate method, since the z variable had default value of 0, you could translate by a vector two by doing:

matrix4.translate(vector2.x, vector2.y)

Here is an example "in the wild" of such usage.

With the new methods, this becomes even less ergonomic, as it would require either calling translateByDouble with 2 extra parameters, or converting the Vector2 to a Vector3.

So I propose we introduce a translateByVector2 which behaves exactly as translate(x, y) would before.

[luanpotter]

note: I shifted the variable names a bit here to make it match some sort of logic with the new names, but please lmk if there is a preferred naming convention.

tbh this test feels like two tests in one but I don't want to change the structure too much.

[coveralls]

coverage: 26.708% (+0.006%) from 26.702%
when pulling 5610bb9 on luanpotter:luan.translateByVector2
into 3939545 on google:master.

[spydon]

@kevmoo could we have a review of this one? :)

[spydon]

@luanpotter tool/generate_vector_math_64.dart needs to be run so that it generates the vector_math_64 file too.

[spydon]

@kevmoo any chance we can get a review on this one, and #351? 😇

[kevmoo]

Please update the changelog! Also the version should (now) be 2.3.0-wip since we're adding a feature!

[luanpotter]

@kevmoo added - I can update the other PR after this is merged so I can rebase the changelogs 🙏

[luanpotter]

actually I think I misunderstood how the changelog works at first - I think it is as intended now