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, 6 insertions, 1 deletions

diff --git a/libbuild2/target-key.hxx b/libbuild2/target-key.hxx
index bd9b8c7..0096d46 100644
--- a/libbuild2/target-key.hxx
+++ b/libbuild2/target-key.hxx
@@ -19,7 +19,7 @@ namespace build2
 {
   // Light-weight (by being shallow-pointing) target key.
   //
-  class target_key
+  class LIBBUILD2_SYMEXPORT target_key
   {
   public:
     const target_type* const type;
@@ -31,6 +31,11 @@ namespace build2
     template <typename T>
     bool is_a () const {return type->is_a<T> ();}
     bool is_a (const target_type& tt) const {return type->is_a (tt);}
+
+    // Return the target name or a pair of names if out-qualified.
+    //
+    names
+    as_name () const;
   };
 
   inline bool