Implement mutable vectors using arrays

[utdemir]

This PR refactors Data.Vector.Mutable.Linear to use Data.Array.Mutable.Linear instead of Unsafe.MutableArray. I also did a few refactors around the Array code.

In summary:

• I exposed unsafeRead and unsafeWrite functions from vectors and array to reduce unnecessary bounds-checking in vector code.
• I changed the type signatures so that the linear collection is the last parameter as opposed to the first. This might be controversial , but IMO it makes it nicer to compose the functions, eg:

Vector.fromList l
  $ \vec ->
    vec
      Linear.& Vector.length
      Linear.& \(vec, Unrestricted oldLength) -> Vector.snoc 42 vec
      Linear.& Vector.length
      Linear.& getSnd
      Linear.& \(Unrestricted newLength) -> Unrestricted $ newLength === oldLength + 1

• Array had a few resize functions with counter-intutive semantics. I replaced them with three functions: allocBeside, growBy and shrinkTo. Let me know if you prefer something else.
• MutableArray, Array and Vector used to require at least one element inside. I removed this constraint. It seems like MutableArray can have 0 length, and therefore there is no reason Array and Vector to have that restriction.

So I'm sorry if this PR is a bit all around the place. I suggest you review the modules in this order:

• Unsafe.MutableArray
• Data.Array.Mutable.Linear
• Data.Vector.Mutable.Linear.
• tests
• Data.HashMap.Linear (only contains changes because of the parameter order change)

[utdemir]

I find this function interesting. It is required since when implementing HashMap's, insertions can cause a new, bigger array to be created. However, we can not use alloc function there since it requires a continuation; and making HashMap insertions take a continuation would be unwieldy.

I wanted to replace it with something more generic, but couldn't figure out how to do it nicely. I think this connects to @aspiwack 's suggestion on #130.

[utdemir]

I replaced this function to return an Unrestricted Int instead of Int, to be more consistent with other functions like read.

[utdemir]

The new version of this function returns a Unrestricted a instead. Since the vector does not contain its values linearly, I think it was overly restrictive.

[utdemir]

Now the Array does not have an extra size parameter, since MutableArray# already comes with a sizeof method.

[aspiwack]

• I changed the type signatures so that the linear collection is the last parameter as opposed to the first. This might be controversial , but IMO it makes it nicer to compose the functions

Whatever I think of this change. It didn't belong to this PR. Additionally, this is not the sort of change that you should make without talking about it first. We've all got better things to do than revert this in the course of this PR, though I do hope this sort of conflation won't happen again. But please open an issue to discuss the order of arguments in these functions. (under the bikeshedding label, I assume)

[aspiwack]

Array had a few resize functions with counter-intutive semantics. I replaced them with three functions: allocBeside, growBy and shrinkTo. Let me know if you prefer something else.

This should have been another PR.

[utdemir]

I'm happy to spend some time sending separate PR's for each. Sorry about this.

[utdemir]

I split this up to #147, #148 and #149. Alongside with the original #144, they should cover all of the changes here.