Make aliases and revisions accessible as subnodes

[barlock]

Overview

As a user-developer, I want to be able to easily access my revisions and aliases so that I can trace history, future, and perform operations like blue/green deploys.

Acceptance

• When a revision is published or alias set, resolve that hash as a subnode of the original
  • if default alias resolves as barlock.eth. then rev 1 resolves as 1.barlock.eth and alias blue resolves as blue.barlock.eth

Tasks

• [ ] Update public resolver contract