tests/test-issue522.t

update: add a Rust fast-path when updating from null (and clean)

This case is easy to detect and we have all we need to generate a valid
working copy and dirstate entirely in Rust, which speeds things up
considerably:

On my machine updating a repo of ~300k files goes from 10.00s down to 4.2s,
all while consuming 50% less system time, with all caches hot.
Something to note is that further improvements will probably happen
with the upcoming `InnerRevlog` series that does smarter
mmap hanlding, especially for filelogs.

Here are benchmark numbers on a machine with only 4 cores (and no SMT enabled)

```
### data-env-vars.name               = heptapod-public-2024-03-25-ds2-pnm
  # benchmark.name                   = hg.command.update
  # bin-env-vars.hg.py-re2-module    = default
  # bin-env-vars.hg.changeset.node   = <this change>
  # benchmark.variants.atomic-update = no
  # benchmark.variants.scenario      = null-to-tip
  # benchmark.variants.worker        = default
default: 5.328762  ~~~~~
rust: 1.308654  (-75.44%, -4.02)
### data-env-vars.name               = mercurial-devel-2024-03-22-ds2-pnm
  # benchmark.name                   = hg.command.update
  # bin-env-vars.hg.py-re2-module    = default
  # bin-env-vars.hg.changeset.node   = <this change>
  # benchmark.variants.atomic-update = no
  # benchmark.variants.scenario      = null-to-tip
  # benchmark.variants.worker        = default
default: 1.693271  ~~~~~
rust: 1.151053  (-32.02%, -0.54)
### data-env-vars.name               = mozilla-unified-2024-03-22-ds2-pnm
  # benchmark.name                   = hg.command.update
  # bin-env-vars.hg.py-re2-module    = default
  # bin-env-vars.hg.changeset.node   = <this change>
  # benchmark.variants.atomic-update = no
  # benchmark.variants.scenario      = null-to-tip
  # benchmark.variants.worker        = default
default: 38.901613  ~~~~~
rust: 11.637880 (-70.08%, -27.26)
### data-env-vars.name               = netbsd-xsrc-public-2024-09-19-ds2-pnm
  # benchmark.name                   = hg.command.update
  # bin-env-vars.hg.py-re2-module    = default
  # bin-env-vars.hg.changeset.node   = <this change>
  # benchmark.variants.atomic-update = no
  # benchmark.variants.scenario      = null-to-tip
  # benchmark.variants.worker        = default
default: 4.793727  ~~~~~
rust: 1.505905  (-68.59%, -3.29)
```

https://bz.mercurial-scm.org/522

In the merge below, the file "foo" has the same contents in both
parents, but if we look at the file-level history, we'll notice that
the version in p1 is an ancestor of the version in p2. This test makes
sure that we'll use the version from p2 in the manifest of the merge
revision.

  $ hg init repo
  $ cd repo

  $ echo foo > foo
  $ hg ci -qAm 'add foo'

  $ echo bar >> foo
  $ hg ci -m 'change foo'

  $ hg backout -r tip -m 'backout changed foo'
  reverting foo
  changeset 2:4d9e78aaceee backs out changeset 1:b515023e500e

  $ hg up -C 0
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

  $ touch bar
  $ hg ci -qAm 'add bar'

  $ hg merge --debug
  resolving manifests
   branchmerge: True, force: False, partial: False
   ancestor: bbd179dfa0a7, local: 71766447bdbb+, remote: 4d9e78aaceee
   foo: remote is newer -> g
  getting foo
  1 files updated, 0 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)

  $ hg debugstate | grep foo
  m   0         -2 unset               foo

  $ hg st -A foo
  M foo

  $ hg ci -m 'merge'

  $ hg manifest --debug | grep foo
  c6fc755d7e68f49f880599da29f15add41f42f5a 644   foo

  $ hg debugindex foo
     rev linkrev       nodeid    p1-nodeid    p2-nodeid
       0       0 2ed2a3912a0b 000000000000 000000000000
       1       1 6f4310b00b9a 2ed2a3912a0b 000000000000
       2       2 c6fc755d7e68 6f4310b00b9a 000000000000