tests/test-debugrename.t

exthelper: reintroduce the ability to register revsets

I think this is what Yuya and Boris agreed on.[1]  This happens *after* the
extsetup phase now (and after the _aftercallback notifications).  But this is
trivial, mergeable between exthelper instances, and doesn't need to have the
extension name supplied when registering.

The test needed updating so that extsetup() takes a `ui` argument, as exthelper
isn't trying to be backward compatible with 1.3.1.

[1] https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-December/125888.html

  $ hg init
  $ echo a > a
  $ hg ci -Am t
  adding a

  $ hg mv a b
  $ hg ci -Am t1
  $ hg debugrename b
  b renamed from a:b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3

  $ hg mv b a
  $ hg ci -Am t2
  $ hg debugrename a
  a renamed from b:37d9b5d994eab34eda9c16b195ace52c7b129980

  $ hg debugrename --rev 1 b
  b renamed from a:b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3