Fix stale Fresh data for multiplayer clients

[user01010111]

Some container details were not included in the multiplayer event payloads, which could leave clients with stale or incomplete information.

This change:

• sends the current fill type with container updates, so fermented bales change from grass to silage on connected clients without requiring a reconnect;
• preserves the pallet flag during container registration and full state sync, so pallet grouping and "Items in World" storage overrides match the server;
• includes storage class information when loss history is sent to a joining client.

The server remains authoritative. This only brings the client's copy of the affected state into line with the server.

Checks completed:

• Lua syntax validation;
• registration, incremental update, and full-sync round-trip checks;
• full-sync coverage for loss entries with and without a storage class;
• modDesc.xml validation against the FS25 1.21 schema.