support for key-layout offset shifting from build config

[Hazno-dev]

key-layout-* on the build config can sometimes specify a 4th value, this value is used to multiply the computed offsets. without using it, all offsets are broken.

in my case, the value was 16. which can be simplified to a 4 byte shift.
it will try determine if it can perform a bit shift instead of multiplying once on init.

Example:

#Config ...
key-layout-index-bits = 0
key-layout-0 = 8 8 40 16


offset = 14755A;              //0x14755A - WRONG
offset = 14755A * 16;    //0x14755A0 - CORRECT
offset = 14755A << 4;   //0x14755A0 - CORRECT

#Config ...
key-layout-index-bits = 0
key-layout-0 = 8 8 40 1


offset = 14755A;              //0x14755A - CORRECT
offset = 14755A * 1;        //0x14755A - CORRECT
offset = 14755A << 0;    //0x14755A - CORRECT

should have no/a negligible effect on existing builds which don't utilize the multiplier.

[Hazno-dev]

for reference: https://github.com/levinium/D2RExtractor/blob/main/D2RExtractor/Services/Steam/StaticContainer.cs#L95

[ZingBallyhoo]

thank