Add updateauth and deleteauth command processing to eosc

[brianjohnson5972]

(Account History API has logic to support these messages, but currently it is untested)

[brianjohnson5972]

Not sure if this needs to have a milestone, but it is not going into EOS Dawn 1.0. It was just addressing that Account History API has logic to support those message types, but we are not currently testing them.

[heifner]

There are a number of items that need to be added for this.
https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md#role-based-permission-management

Currently reviewing what additional functionality is required to provide the role-based permission management.

[heifner]

• Add linkauth to eosc. The message type already exists.
• Add unlinkauth to eosc. The message type already exists.
• Add updateauth to eosc. The message type already exists.
• Add deleteauth to eosc. The message type already exists.

[wanderingbort]

Somehow I missed this when consolidating tasks into #402

That has links to issues where @bytemaster described the desired interface in eosc for managing auths

It seems like we will be stepping on each others toes. How much work is wasted if we close this issue as a duplicate of #402?

[heifner]

Closing as duplicate of #402.