Overhaul of I-Note Generation

### Problems:

- Process of generating I-Notes uses excessive string searching
- Adding a feature to one file type (epub, pdf, html, latex) means we need to rewrite and change code for all the other file types
- Creating new file output types makes this problem worse

### Possible Solutions
- Use a Sax Parser and Callback functions to automatically generate content (title, text, image, etc...) for each output type without having to make a different file for each type. [example](https://www.baeldung.com/java-sax-parser)

The issue names no files, tests, or entry points. Start by locating I-Note generation for epub, PDF, HTML, and LaTeX, then compare how each output type searches and assembles strings. Done means the generation approach supports shared content handling and adding output types without rewriting every existing format.

Written by the indexing model from the issue text.