Fix BoolRegister.ReadAsync reading the DT area instead of X/Y/R

ReadAreaByteRangeAsync takes an areaPrefix parameter that defaults to
RegisterPrefix.DT. BoolRegister.ReadAsync did not pass it, so a direct
read of a bit register resolved against the data area rather than the
bit area: reading R183 actually read DT18 and returned bit 3 of that
word. Reads silently returned wrong values rather than failing, and on
a PLC whose low DT registers happen to be zero every bit register reads
as false.

The address itself was resolved correctly (GetMewName/MemoryAddress),
and the write path (WriteSingleBitAsync) was already correct, so only
reads were affected. AreaBase already passes registerType through, so
the polled path was unaffected too - this only hit direct ReadAsync.

Verified against an FP-series PLC over MEWTOCOL by comparing against
raw RCC word reads (WR18 = 0x82A8, WX0 = 0x000D): 12 of 12 bit
registers across the R and X areas now match, where previously all 12
returned false.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: SeanMollet

MewtocolNet/Registers/Classes/BoolRegister.cs

@@ -116,7 +116,9 @@ private async Task<bool> WriteSingleBitAsync(bool val) {
         /// <inheritdoc/>
         public async Task<bool> ReadAsync() {
 
-            var res = await attachedInterface.ReadAreaByteRangeAsync((int)MemoryAddress, (int)GetRegisterAddressLen() * 2);
+            //pass the register type, otherwise this falls back to the DT area default and
+            //reads a data register instead of the X/Y/R bit area
+            var res = await attachedInterface.ReadAreaByteRangeAsync((int)MemoryAddress, (int)GetRegisterAddressLen() * 2, RegisterType);
             if (res == null) throw new Exception($"Failed to read the register {this}");
 
             var matchingReg = attachedInterface.memoryManager.GetAllRegisters()