[FIX] ExcelReader: Write roles

[VesnaT]

Issue

Fixes #5798

Description of changes

Beside headers, also save types and flags.

Includes

• Code changes
• Tests
• Documentation

[markotoplak]

From the code it seems that headers are always written, but this should, instead, respect users' setting in the widget.

Furthermore, for backward compatibility, the add type annotations could get disabled when opening saved workflows that save to Excel.

[codecov]

Codecov Report

Merging #5810 (ee88eeb) into master (dfd2734) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5810      +/-   ##
==========================================
- Coverage   86.14%   86.13%   -0.01%     
==========================================
  Files         316      316              
  Lines       66388    66398      +10     
==========================================
+ Hits        57187    57191       +4     
- Misses       9201     9207       +6     

[VesnaT]

From the code it seems that headers are always written, but this should, instead, respect users' setting in the widget.

I wasn't even aware we have that. I'll fit it.

Furthermore, for backward compatibility, the add type annotations could get disabled when opening saved workflows that save to Excel.

I'm not sure I want to support backward compatibility for something that didn't work correctly.

[markotoplak]

Furthermore, for backward compatibility, the add type annotations could get disabled when opening saved workflows that save to Excel.

I'm not sure I want to support backward compatibility for something that didn't work correctly.

My perspective on this is that for some users, especially for those that saved those workflows, the output was exactly what they needed or they somehow adapted to. Perhaps they just accepted that type setting as something that does not apply to Excel files. If they loaded their workflows after the changes, the saved files are going to change, which can lead to problems later on.

The number of users relying on this is likely small and perhaps we can ignore them and just break things for them... But on the other hand, supporting that here is easy: we could just add the rule on setting open if setting_version_old and use_excel: value_setting = False. So no special support of old behaviors, just setting change.