We expect that a user may copy this file and uses it as a starting
point for their own configuration.

When they do that, we don't want them to freeze the default config in
time.  Instead, we can expect them to uncomment settings they wish to
change.  Then when they upgrade arti, *other* settings will get the
new defaults, which I think is right.

Now,
  git-grep '^#[^ ]' crates/arti/src/arti-example-config.toml
has no ouptut.

This prepares us for the next commit.

The defaults are built into the code.  This is a doc-commented example
file, not the primary specification of what the defaults are.

This is redundant, because the defaults have to be supplied by the
config builders (usually via builder default attributes).

That this is actually done and correct is tested by the
`default_config()` test case in arti/src/cfg.rs.

Add this test even though our construction of the Default and Builder
ought to trivially ensure that it's true.

arti-config: Move cmdline to tor-config

See merge request tpo/core/arti!498

Improvements prompted by clippy, and disable one lint

See merge request tpo/core/arti!497

Provide and use macro for impl Derive via Builder

See merge request tpo/core/arti!499

Add correct serde(default) attrs for humantime_serde::option

See merge request tpo/core/arti!502

Discovered by a test case in my local tree.  The test case was
macro-generated by an extension of impl_standard_builder (which
macro istself currently awaiting review, arti!499)

Have also sent an MR to update the upstream docs
  https://github.com/jean-airoldie/humantime-serde/pull/8

The type of ret.map_err(codec_err_to_chan)? is ().  ISTM that
writing `let () = ` makes it clear that there is nothing there,
but the lint forbids this.

This lint is warn by default and trips here for me on current nightly.

It seems wrong to me.  We should be able to make it clear to the
reader that there is nothing here - note how this differs from the
lines below where Ready contains msg.  A let () binding is a good way
to do that.

I think the lint allow ought to be added everywhere, but that doesn't
seem easy right now - see this issue about maint/add_warning:
   tpo/core/arti#469

This does involve unwrap, but of course that can't fail unless the
formats fail, which would already panic (that's implied by format!).

This does not know anything about arti, only about TOML and Config.

Code motion, plus necessary import adjustments.

Tidy up ConfigurationSource a bit

See merge request tpo/core/arti!495

This will let other embedders use it.

These generic arguments weren't consistent.  It doesn't make sense ot
insist on getting a borrowed type and then cloning it.  So tidy things
up in the direction of taking owned values, which is what
ConfigurationSources actually needs.

(My personal preference would be &dyn to avoid monomorphisation code
bloat but that was controversial last time I proposed it somewhere.)

Discarding this error is not right.

It is not clear to me how this `pub enum` survived the "inaccessible
pub" lint.

This emphasises its nature.  We're going to provide a more cooked
constructor in a moment.

Improve documentation around Cargo features; make Runtime require Debug

Closes #445

See merge request tpo/core/arti!496

- #445 highlighted the lack of good documentation around Arti's
  multiple runtime support, as well as it being difficult to determine
  what runtime was actually in use.
- Improve the documentation to solve the first problem.
- To solve the second problem, make Runtime require Debug (which is
  arguably a good idea anyway, since it makes them easier to embed in
  things), and print out the current runtime's Debug information when
  arti is invoked with `--version`.
- (It also prints out other Cargo features, too!)

fixes #445

Refactor the tor-dirmgr bootstrapping code more gracefully

See merge request tpo/core/arti!488

Disable fs-mistrust in coverage CI.

See merge request tpo/core/arti!493

Remove cargo-husky, and replace with manual instructions

See merge request tpo/core/arti!494

A build script reaching into your .git/hooks/ and modifying them
nonconsensually was a bit of a horrifying concept, and also made it hard
to build arti with the feature disabled. Remove this crate, and replace
it with manual instructions on how to install the hooks in
CONTRIBUTING.md.

- Some FIXMEs got removed or amended.
- AddMicrodescs now yields a mutable reference, so we can use .drain()
  and reuse the allocation.
- Some panics were downgraded to debug_asserts.

- We don't want to inadvertently replace our netdir with one that's
  actually older, so detect and error on this condition.
- Also, print a debug line when we get a new netdir without enough
  guards.
- (An unrelated TODO was also added.)

- Taking a previous netdir directly and keeping it around before we need
  it is a bit of a waste of memory, and also doesn't mesh well with how
  SharedMutArc works.
- To remedy this, introduce a new trait `PreviousNetDir` and have the
  state machines take that instead. (I was a bit tempted to just pass in
  the SharedMutArc directly. Maybe I should've done that.)

The CI runners like to run as root with umask 000, which our code
rightly freaks out about.