vote: use InvalidAccountData for v0_23_5 vsv deserializing

[mjain-jump]

In FD, we have get_state() implemented and used instead of implementing Agave's custom deserializers for vote states. To simplify the deserialization logic, InvalidAccountData should be thrown to match the error semantics of get_state() in fuzz-generated cases where v0_23_5 vote accounts have invalid data.

[buffalojoec]

Originally I did this on purpose, since we decided v0 accounts would be treated as uninitialized, since they're phased out.

We can either do this here, to align with the v3 and v4 deserializers...

solana-sdk/vote-interface/src/state/vote_state_v3.rs

Line 192 in e9de9d8

Err(InstructionError::InvalidAccountData)

solana-sdk/vote-interface/src/state/vote_state_v4.rs

Line 174 in e9de9d8

Err(InstructionError::InvalidAccountData)

...or we can use UnitializedAccount everywhere.

I suppose InvalidAccountData is closer to the actual case itself - the account layout is invalid, because it's been phased out. I vote ship it.