Always provide the vector metatable to node callbacks

[j-r]

Use vector.new/copy/offset as appropriate and replace deprecated use of vector.new by vector.copy.

Background

While doing their redstone rewrite Mineclonia decided to make aggressive use of the vector metatable and assume that it is present when positions are passed to standard callbacks (see https://codeberg.org/mineclonia/mineclonia/issues/3820). This worked out surprisingly well and it seems feasible to update mods that don't always provide the metatable. Digtron already uses vector.new in some places and this PR consistently replaces all manually created position vectors with the appropriate vector constructor.

Testing

There should be no change in digtron behavior.

[j-r]

Added a commit that adds a message when run on old Luanti or MTG versions as well as adding polyfills, and a 2nd one with min_minetest_version.

I was quite happy with these until I noticed that fakelib is already using vector.copy. Aargh:-)

I think I'll mostly remove the polyfill commit and just keep the message (upgraded to an error) after testing for vector.copy and default.set_inventory_action_loggers and merge with the min version commit. This should also fix the luacheck problem.

[j-r]

This seems to be ready now. It errors out if Luanti is too old, but falls back with warning if default mod doesn't have set_inventory_action_loggers (it might be some compatibility layer instead of MTG, after all).

[SmallJoker]

Looks good. Thank you for the adjustments.
Will merge in a few days unless there are objections.