bugfix(saveload): Keep the dark low power appearance on disabled objects when saving

[bobtista]

Fixes #3126. Follow up for #1651, which changed TintEnvelope::m_sustainCounter from UnsignedInt to Real.

The retail compatible save path still round-trips that counter through an UnsignedInt. SUSTAIN_INDEFINITELY is 0xfffffffe, and (Real)0xfffffffe rounds up to 4294967296, which is out of range for UnsignedInt — so converting it back is undefined, and on MSVC it yields 0 (checked on both x86 and x64). Because TintEnvelope::xfer assigns the converted value back into m_sustainCounter, this fires on save as well as load: the live counter becomes 0, the envelope leaves its sustain branch on the next update and calls release(), and the object stops being drawn dark while it is still disabled. RETAIL_COMPATIBLE_XFER_SAVE defaults to 1, so this is the shipping path. It also writes 0x00000000 where retail wrote 0xfffffffe, defeating the byte compatibility the guard exists to preserve.

Affected are the objects drawn dark indefinitely: unpowered and otherwise disabled objects, subdual damaged objects, and frenzied objects.

Now maps the sentinel explicitly in both directions so the v1 stream keeps retail's 0xfffffffe, and only assigns the serialized value back when loading, so saving can no longer change live state. Finite sustain values serialize exactly as before, so existing saves are unaffected.

Verified in game on a clean build of main using the reproduction in #3126 — an unpowered Patriot Missile System loses its dark drawing within seconds of a save on main, and keeps it with this change. Mean brightness of the Patriot's area on screen:

stage	main	this branch
before saving (unpowered, dark)	83.8	87.4
immediately after saving	95.2	76.1
5s after saving	99.1	84.2
15s after saving	107.1	88.6

Before:

After:

Todo:

• Test that an unpowered structure stays dark across a save
• Test save/load round trip restores the dark drawing
• Replicate to Generals