`Enum` trait allows type confusion when manually implemented

Summary

Affected versions of this crate did not require the element type of the `Array` associated type in the `Enum` trait to match the array's generic parameter `V`.

This can result in type confusion, and consequently memory corruption, when a manual `Enum` implementation declares an `Array<V>` whose elements are not actually of type `V`:

```rust struct IntentionallyWrong;

impl Enum for IntentionallyWrong { type Array<V> = [String; 4];

fn from_usize(_: usize) -> Self { IntentionallyWrong }

fn into_usize(self) -> usize { 0 } }

enum_map! { IntentionallyWrong => 42 }; ```

The flaw was corrected in commit [7a8b815432](https://codeberg.org/sugar700/enum-map/commit/7a8b8154323d426415a10accf104cd05c394cda9) by adding a `Value = V` bound to the `Array` type in the `Enum` trait.