`&` shadows the same operator in `Data.Function` in `base`

`&` is usually [reserved](https://hoogle.haskell.org/?hoogle=%26) for a function of type [`a -> (a -> b) -> b`](https://hoogle.haskell.org/?hoogle=a-%3E(a-%3Eb)-%3Eb), but superrecord's `&` shadows it

Also, because of #17, it's impossible right now (with the hackage version) to just re-export it with a different name.

I understand that changing that name would be a huge breaking change, how about deprecating it and using something else? I'd use `&=`, but I must admit I haven't surveyed the conventions enough to be confident in my suggestion