Rework tool importation along with cli module

Specifically, now config.<tool> (like config.cli) is handled by the import
machinery (it is like a shorter alias for config.import.<tool>.<tool>.exe
that we already had). And the cli module now uses that instead of custom
logic.

This also adds support for uniform tool metadata extraction that is handled by
the import machinery. As a result, a tool that follows the "build2 way" can be
imported with metadata by the buildfile and/or corresponding module without
any tool-specific code or brittleness associated with parsing --version or
similar outputs. See the cli tool/module for details.

Finally, two new flavors of the import directive are now supported: import!
triggers immediate importation skipping any rule-specific logic while import?
is optional import (analogous to using?). Note that optional import is always
immediate. There is also the import-specific metadata attribute which can be
specified for these two import flavors in order to trigger metadata
importation. For example:

import? [metadata] cli = cli%exe{cli}

if ($cli != [null])
  info "cli version $($cli:cli.version)"

1 files changed, 3 insertions, 1 deletions

diff --git a/libbuild2/utility.hxx b/libbuild2/utility.hxx
index 3a5e708..9800d6c 100644
--- a/libbuild2/utility.hxx
+++ b/libbuild2/utility.hxx
@@ -579,7 +579,7 @@ namespace build2
   void
   append_options (sha256&, T&, const char*);
 
-  // As above but from the strings value directly.
+  // As above but from the lookup directly.
   //
   LIBBUILD2_SYMEXPORT void
   append_options (cstrings&, const lookup&, const char* excl = nullptr);
@@ -590,6 +590,8 @@ namespace build2
   LIBBUILD2_SYMEXPORT void
   append_options (sha256&, const lookup&);
 
+  // As above but from the strings value directly.
+  //
   void
   append_options (cstrings&, const strings&, const char* excl = nullptr);