fix(store): query only latest vault rows when applying account delta

[TomasArrachea]

While testing for 0xMiden/miden-client#1843, I made some changes to the node seed store binary and bumped into this bug.

When applying a partial account delta, the store reconstructed the AssetVault by querying all historical vault rows instead of only the current state. This caused DuplicateAsset error when the same vault key had entries across multiple blocks. i.e., after 2+ balance updates to the same faucet for an account. This is way the current test did not catch the error, I updated it to update the account 3 times and it fails.

The fix is to replace the historical range query with a new select_latest_vault_assets function that filters on is_latest = true, returning only the current vault state for reconstruction.

[drahnr]

Thank you!

[Mirko-von-Leipzig]

@drahnr do we need this on main as well?

[drahnr]

Suggested change

	let mut assets = Vec::new();
	for (_vault_key_bytes, maybe_asset_bytes) in entries {
	if let Some(asset_bytes) = maybe_asset_bytes {
	assets.push(Asset::read_from_bytes(&asset_bytes)?);
	}
	}
	Ok(assets)
	Result::from_iter(entries.into_iter().filter_map(|(_vault_key_bytes, maybe_asset_bytes)| { maybe_asset_bytes.map(Asset::read_from_bytes).transpose()}));

[drahnr]

The code in question was changed in #1538 ( 965282b74 ), which is not present on main. So next should be sufficient.