Implement a better diff view for multiple versions of the file format layout tables

[rdw-software]

Copy/pasting the Markdown tables is easy, but keeping them consistent will be a perpetual maintenance nightmare.

I also think it's a bit unfortunate that minor differences can't be depicted somehow. Ideally, there'd be a tab selector that can be used to display the full layout for any of the versions - maybe even with a green highlighted table row for the changes from the last version. A simpler alternative would be to just hide/show fields based on the selected version, which seems doaable.

If this is too difficult to actually implement, an alternative idea would be defining C-like structs and literally a git diff (colored, GitHub style) on the different versions, then insert as an image (or something like that) if needed... That won't be great for maintenance, though.

[rdw-software]

Should be easy enough to do using this Docusaurus feature: https://docusaurus.io/docs/markdown-features/tabs

[rdw-software]

There's some issues with just switching over all the layout tables to a tab view:

• The field sizes vary a lot due to the dynamic nature of their contents
• There's no good way to highlight differences even without the "jumping" layout
• Shared fields still have to be duplicated, but inside the JSX code
• Interleaving JSX with the markdown table is even messier and difficult to read

I wonder if maybe separating the types and fields from the descriptions would work better?

Currently, the layout tables include both the structure definitions as well as a basic description of the contents. Due to the space constraints, there isn't enough room to make the descriptions actually useful however. Additionally, manually writing down offsets and lengths is somewhat tedious and error-prone, while being of limited usefulness. I reckon actual code would be more useful.

Perhaps a different approach may yield better results:

• Instead of layout tables, list a C-style type definition that implicitly covers the offset/length part
• Provide explanations separately, either in the format spec or the relevant rendering page that deals with the format
• The main issue here is that variable-length arrays can't easily be expressed in any of the static type systems

As a workaround, one could use a template-like syntax such as that used by imhex or 010 - but that's even less universal.