fix: decoder component expansion

[muktihari]

Previous implementation of component expansion does not accommodate containing field's value more than 32 bits. This results in expanding incorrect components for messages that has more than 32 bits such as "Hr" event_timestamp_12 (up to 120 bits) and "RawBbi" data (up to 240 bits).

By design, field's value requiring expansion can hold up to 255 bytes (2040 bits) data, this is obviously way more bits than Go's primitive single value can hold. To handle this, I implement new type "bits" struct that can store up to 2048 bits data, enable us to do bitwise operation over it for component expansion.

To test the correctness, I use sample data from "testdata/from_official_sdk/activity_poolswim_with_hr.csv", as it contains 96 bits data to be expanded and the new implementation produces the correct values as in the CSV file.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.94%. Comparing base (aa68a94) to head (3e8383d).

Additional details and impacted files

@@           Coverage Diff            @@
##           master     #474    +/-   ##
========================================
  Coverage   99.94%   99.94%            
========================================
  Files          42       42            
  Lines        3689     3816   +127     
========================================
+ Hits         3687     3814   +127     
  Misses          2        2            

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.