[Feature] Move to rust-norg parser

[NTBBloodbath]

This feature request proposes migrating Norgolith's Norg parsing functionality from a combination of tree-sitter and norg-pandoc to the rust-norg library.

Motivation

The current approach using tree-sitter offers speed benefits but might have limitations in error recovery and accuracy.

rust-norg offers several advantages:

• Robust Parsing: utilizes chumsky for robust parsing, potentially leading to improved error handling and more accurate Norg content representation than using pandoc for converting the Norg documents.
• Error Recovery: the parser's design allows for better error recovery capabilities, potentially leading to a smoother development experience for users encountering syntax issues.
• Native Rust Integration: being written in Rust aligns well with Norgolith's overall architecture and could potentially improve performance and simplify code maintenance.
• MacOS Support: setting up tree-sitter for Norg parsing on macOS can be challenging due to known limitations and potential compilation issues.

Potential Benefits

• Enhanced User Experience: more accurate parsing with better error handling can lead to a smoother workflow for Norg content creators.
  • Users, especially those on MacOS, can benefit from a simpler installation and setup process.
• Improved Code Maintainability: a native Rust library could simplify the codebase and potentially improve performance.
• Reduced Dependencies: eliminating the need for tree-sitter and norg-pandoc could streamline Norgolith's dependency management.

[NTBBloodbath]

NB: README will also need to be updated to reflect those changes once made.

[NTBBloodbath]

Update: I'm currently working on a still private library called rust-norg-html (probably gonna rename it to rust-norg-converter) based on the rust-norg parser. The library is currently on hold until a non-flat NorgAST is produced in the rust-norg library so I can e.g. make proper HTML lists with nested elements.

[NTBBloodbath]

Update: the conversion library is currently embedded in the code and working, once it is much more complete it will be separated into a library that will be added as a dependency to the project.