feat(sdk): Add jumbf_io::remove_jumbf_from_stream

[stupside]

Fixes #2451.

Changes in this pull request

jumbf_io publishes memory, stream and file forms of load and save, but only the file form of remove:

	memory	stream	file
load	load_jumbf_from_memory	load_jumbf_from_stream	load_jumbf_from_file
save	save_jumbf_to_memory	save_jumbf_to_stream	save_jumbf_to_file
remove			remove_jumbf_from_file

remove_jumbf_from_file is gated on file_io, so with that feature off there is no public way to remove a manifest store at all. The capability is already there: every asset handler implements CAIWriter::remove_cai_store_from_stream, and the file form is a thin dispatch over the path equivalent. Only the public entry point was missing.

This adds the sibling, dispatching through get_caiwriter_handler exactly as save_jumbf_to_stream does and returning Error::UnsupportedType for a format with no writer:

pub fn remove_jumbf_from_stream(
    asset_type: &str,
    input_stream: &mut dyn CAIRead,
    output_stream: &mut dyn CAIReadWrite,
) -> Result<()>

The doc comment refers to remove_jumbf_from_file in backticks rather than as an intra-doc link, since that item does not exist in a build without file_io and the link would dangle there.

Checklist

• This PR represents a single feature, fix, or change.
• All applicable changes have been documented.
• Any TO DO items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.

Tests

test_jumbf, the helper behind the per-format test_streams_* tests, already wanted this operation and had no public function to call, so it resolved the handler itself:

let handler = get_caiwriter_handler(asset_type).unwrap();
let mut removed = Cursor::new(Vec::new());
handler
    .remove_cai_store_from_stream(&mut writer, &mut removed)
    .unwrap();

It now calls remove_jumbf_from_stream, so the new function is covered for every format that helper runs: jpeg, png, webp, tiff, svg, mp3, wav, avi, mp4, heif, heic, avif, jxl and c2pa. That replaces the hand-rolled dispatch rather than adding a parallel test for it.

test_remove_jumbf_from_stream_unsupported_type covers the dispatch failure, which the per-format tests cannot reach.

cargo test -p c2pa --lib jumbf_io is green (21 tests), as are cargo fmt and cargo clippy --all-targets. cargo check --no-default-features passes, since being available without file_io is the point of the function.