Reintroduce domain deprecation

[kronosapiens]

Closes #1279

This PR restores the ability to deprecate domains and local skills. It also moves skills deprecation entirely to the colony level and away from the network, completing the process begun in #1173.

There are two migration considerations, both of which I believe are relatively minor:

• The current localSkills boolean mapping is deprecated and replaced by a LocalSkill struct mapping. For already-extant local skills, validity and deprecation behaviors are preserved.
• Due to the "deprecation of deprecation" on the colony network, all currently-deprecated skills will become "undeprecated". Affected users will need to re-deprecate any skills or domains such affected.

The point to emphasize is that these migration issues affect functionality that has been deprecated for some time. As such, the actual effects are likely to be very minor.

TODO:

• Add upgrade test for local skill deprecation

[area]

What on earth has happened to .storage-layouts-normalized?

[area]

Implementation looks good. Just need to work out how to convince myself further that it won't brick everything with the return data change when calling getDomain.

[area]

I spent this afternoon getting extremely comfortable with Remix and EVM Opcodes to convince myself further that returning too much data in a call is okay, and I believe it is. I might end up adding to the relevant OneTxPayment test though.

I also don't believe bricking the mining cycle is a risk after all, as the only getDomain() call is in the initialization, so that makes me a little happier. I still don't want to merge this until after multisig has been merged and deployed, though.

[area]

Still waiting on multisig.

That's now merged, but not yet deployed... so closer, at least!

[area]

Needs #1299 merged, and then versions bumped accordingly.