Make Notare style and table XML schema-compliant

Correct the remaining Open XML schema-ordering errors in Notare-generated DOCX packages. Observed with the Open XML SDK validator on the regenerated protocol sample: - 9 errors in `word/styles.xml`: style run properties contain unexpected `w:b`, `w:i`, or `w:color` children because `w:rPr` children are emitted outside the `CT_RPr` sequence. - 4 errors in `word/document.xml`: styled tables emit `w:tblStyle` after table width/layout properties, although `CT_TblPr` requires the table style earlier. Scope should include auditing the relevant style, run-property, and table-property renderers for schema-required child order rather than patching only the sampled combinations. Acceptance criteria: - Built-in and custom style run properties follow the WordprocessingML schema order. - Direct text-run property combinations follow the schema order. - Styled table properties follow the WordprocessingML schema order. - Regression tests cover representative combined run properties and styled tables. - A representative generated DOCX has no Open XML SDK validation errors attributable to styles or table properties. - The full Notare test suite and RuboCop pass.