Files generated with version 3.2.0 fail to load in various applications

Hi,

Some CloudCompare users have reported that the files saved with version 3.2.0 of libE57Format won't open with Rhino8, SolidWorks 2023 and FARO Scene. Reverting to version 3.1.1 seems to fix the issue.

It seems to be related to this commit: feaa963f704ab5b677ad8978c4f9a42f0ceb145d (I've generated files with version 3.2.0 with only this commit reverted, and it seems to work fine). Even though it seems to be 'required by the standard', I guess these SW solutions are not able to handle the single CV index packet properly?

Maybe a solution would be to add a boolean somewhere to control whether this CV index packet should be automatically added or not? (with a default state to true)

@dancergraham I've attached a file that fails to load with the above applications. [pumpsA_3.2.0.e57.zip](https://github.com/user-attachments/files/17607824/pumpsA_3.2.0.e57.zip)

Start by inspecting commit feaa963f704ab5b677ad8978c4f9a42f0ceb145d and comparing its output with libE57Format 3.1.1; use the attached pumpsA_3.2.0.e57 file as the compatibility reproducer. Determine how the single CV index packet affects Rhino8, SolidWorks 2023, and FARO Scene, then verify that generated files load in those applications without breaking the E57 standard behavior.

Written by the indexing model from the issue text.