Moves 0 for write_version in geyser when restoring from a snapshot

[brooksprumo]

Problem

We are trying to move account storage files away from using mmaps internally. The function StoredAccountMeta::set_meta() updates the underlying mmap, which will not be possible once mmaps are removed. (It's also not supported for Tiered Storage at all.)

agave/accounts-db/src/account_storage/meta.rs

Lines 174 to 181 in 70c4cb0

	pub fn set_meta(&mut self, meta: &'storage StoredMeta) {
	match self {
	Self::AppendVec(av) => av.set_meta(meta),
	// Hot account does not support this API as it does not
	// use the same in-memory layout as StoredMeta.
	Self::Hot(_) => unreachable!(),
	}
	}

The only caller of set_meta() is in geyser, when restoring from a snapshot.

We use set_meta only to set the write version to zero. Instead, we can move this 0 literal inside accountinfo_from_stored_account_meta(), which is only called when restoring from a snapshot. This ensures we do not change behavior at all, and allows us to remove the call to set_meta().

Summary of Changes

Moves where 0 is set for write version.

This PR is effectively a combination of #721 and #702.

[jeffwashington]

lgtm