Calls to XmpFile::close can abort process if C++ XMP Toolkit throws an exception

[scouten-adobe]

When calling XmpFile::close, any situation which would cause the underlying C++ code to raise an exception resulted in a process abort because there was no code to translate the C++ exception to a Rust error result.

This is best demonstrated in #230, where a race condition caused the close call to fail due to file I/O errors.

This was fixed in #232 (crate version 1.9.0), which now safely handles the exception.

For backward compatibility, the existing API ignores the error. A new api XmpFile::try_close was added to allow callers to receive and process the error result.

Users of all prior versions of xmp_toolkit are encouraged to update to version 1.9.0 to avoid possible process aborts.

[scouten-adobe]

Fixed in 1.9.0. Using this issue to document the issue for RUSTSEC database.

[scouten-adobe]

Filed as https://rustsec.org/advisories/RUSTSEC-2024-0360.html.