Publish aragonOS internal apps to aragonPM

[sohkai]

Not quite sure how we should do this, since aragonCLI assumes we use a one-contract-per-repo structure, but we should publish the ACL, EVMScriptsRegistry, and Kernel to aragonAPM with their associated artifact metadata (see https://github.com/aragon/aragon.js/blob/master/packages/aragon-wrapper/artifacts/aragon/).

Maybe we could specify a contract address when creating a new repo, and then publish from a different directory that holds the metadata?

[sohkai]

We could also think about doing this for the DAOFactory, since it's used by so many kits: aragon/dao-templates#64

[sohkai]

Notes from an offline discussion:

• Investigate if upgrading to truffle 5 allows us to get the natspec docs so we don't have to use our own regex in the CLI (solidity-extractor)
• Investigate how difficult it would be to generate ACL and EVMScriptsRegistry's artifact.jsons and upload them to IPFS by hand
• Publish new versions of apm-* internal repos with their artifacts