Refactor Basin's behaviour on Contraptions

[vercte]

This PR refactors how basins work on contraptions.

It adds a MountedItemStorage and a MountedFluidStorage for basins on contraptions, both of which take the basins input/output section into account.

It also adds a BasinInteractionBehaviour that lets players right-click a basin on a contraption to take the items out; just like it would work in-world.

It also refactors BasinMovementBehaviour to use and update these storages accordingly. Additionally, this behaviour checks every tick in order to pick up items.

Finally, this adds methods to render the basin correctly in-contraption, including fluids and items.

Gameplay Changes

• Basin can now be accessed inside a contraption with a Portable Storage Interface or Portable Fluid Interface
• Basin can now be emptied of items inside a contraption via a player right-clicking it with an empty hand (just like it works outside of a contraption)
• Fluids are now visible inside a basin when on a contraption
• A basin can dump its contents multiple times (if the items inside it are updated)

[vercte]

Currently, the LerpedFloat dictating the visual basin fluid fill level doesn't persist between syncs; this makes it jump immediately to the current fill level, unlike a in-world basin. I may use the codec to sync the fill level, but I'm not sure yet.

Some stuff I'd like to be double-checked on is my use of the codec and my modification of the non-basin classes, mainly BlockEntityRenderHelper (separating out the light calculation methods) and CreateCodecs (adding a basin inventory codec)

[techno-sam]

The checking every tick to pick up items may be problematic: there's a decent chance it breaks existing factories, and it may add not-insignificant lag to trains which use basins for decoration. I would suggest making that feature opt-in configurable.

[adaliszk]

Hmm, perhaps this should use the same as funnels, where the visitNewPosition() runs the actual pickup logic.

The general expectation is that any contraption actor is ticked via the tickContraption() at the end of the tick cycle only when their defined activation area offsets visit a new world position.

[vercte]

The checking every tick to pick up items may be problematic: there's a decent chance it breaks existing factories, and it may add not-insignificant lag to trains which use basins for decoration. I would suggest making that feature opt-in configurable.

Would it be fine if I made a config for both Basins+Funnels?
As in, a config to switch between tick-pickup and visit-new-block-pickup, since I always found the latter to be odd and not how I'd expect it to work