Include break nodes in DOCX documents

[matteolutz]

Description

This PR aims to provide a way to deserialize line and page breaks in DOCX documents (w:br nodes). This feature is behind a new config flag.

Changes

• Added new config flag includeBreakNodes that is set to false by default.
• Added new union variant break to OfficeContentNodeType and a new metadata type BreakMetadata containing information about the break type (lineWrapping, page or column) and the break clear behaviour.
• Added parsing logic in parseWord.
• Updated the documentation to reflect those changes.

Which internal parser/component does this affect?

• WordParser (DOCX)
• PowerPointParser (PPTX)
• ExcelParser (XLSX)
• OpenOfficeParser (ODT/ODS/ODP)
• PDFParser
• OCR / Worker Pool
• Infrastructure / Build / CLI
• Other (Specify Below)

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (Specify Below)

Verification Results

Please describe the tests you ran to verify your changes.

• Build Check: I have run npm run build and no errors occurred in Node or Browser bundles.
• Parser Baselines: I have run npm test and there are no failures.
• Manual Proof: Provide a brief snippet or screenshot of the new behavior/output.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[harshankur]

Thank you for the PR. I have requested a few changes. Please do them.
Additionally, you did update the docs in the page for officeParser but not the README itself. Please update it too.
Further, please add tests for this as well to check that. Once you do it, run npm test baseline to generate the new baseline json file for docx also. Manually verify its information is exactly how you expect it. Commit that as well.

And please squash your changes.