fix: decoder component expansion on handling edge case

[muktihari]

This PR update component expansion logic on handling edge case such as when a message already has field with the same field number as the expanded field candidate (component field). For such cases, the value of the field will be updated, including the component expansion that is propagated.

For a case like this, typically, the value of the field is the same with the value of the expanded field. For example a record message has speed and enhanced_speed with the same value before the expansion, after the expansion the value will be the same.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (190e0e4) to head (e85a983).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #484   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           42        42           
  Lines         3848      3853    +5     
=========================================
+ Hits          3848      3853    +5     

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