Adaptive domain separator

[LHerskind]

The staked token implementation writes DOMAIN_SEPARATOR to storage in initialize. It will therefore not be able to handle a hard fork post-deployment, as the chainID is not updated and a valid signature for one chain could be replayed on the other.

The issue can be handled by using a dynamic domain separator which is generated on demand instead of reading from storage.