Update RTDE list to include new fields

[URJala]

Also reordered the fields to match the documentation order.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.56%. Comparing base (9e52693) to head (be63761).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #380      +/-   ##
==========================================
- Coverage   77.95%   77.56%   -0.40%     
==========================================
  Files          92       92              
  Lines        4165     4163       -2     
  Branches      461      461              
==========================================
- Hits         3247     3229      -18     
- Misses        682      695      +13     
- Partials      236      239       +3     

Flag	Coverage Δ
start_ursim	82.15% <ø> (-2.35%)	⬇️
ur20-latest	75.60% <100.00%> (-0.18%)	⬇️
ur5-3.14.3	76.10% <100.00%> (-0.19%)	⬇️
ur5e-10.7.0	71.18% <100.00%> (+0.35%)	⬆️
ur5e-5.9.4	76.06% <100.00%> (-0.13%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[urfeex]

To which documentation did you do the reordering? It doesn't match https://docs.universal-robots.com/tutorials/communication-protocol-tutorials/rtde-guide.html#field-names-and-associated-types

[URJala]

It does match that one, except for the fields which are both input and output, those have been grouped by them selves, because they would otherwise need to appear twice. So other than "input_yyyy_register_X" it should be the same.

[urfeex]

Could you please also update https://github.com/UniversalRobots/Universal_Robots_Client_Library/blob/9e5269319fac311e428d36d260f25678a546ec16/tests/resources/exhaustive_rtde_output_recipe.txt?

And we should probably remove the output_bit_register_0..63 and input_bit_register_0..63 fields at some point. Though, it would probably make sense to take that to a separate PR in order to show up in the changelogs properly.