Check for mutable bounds in Phantom or PhantomBase

[antonagestam]

Related to #128, I'm realizing there's more we can do to eliminate the risk of users using phantom types with mutable bounds. The check from sized can be reused but made to raise at import-time. It would also make sense to check for non-frozen dataclasses, and perhaps even to check dataclass fields.