Refactor build steps to generate blueprints instead

The blueprint is generated at the root of the repository and is
  intended to be versioned with the rest. It acts as a business card
  that contains many practical information. There's a variety of tools
  we can then build on top of open-source contracts. And, quite
  importantly, the blueprint is language-agnostic; it isn't specific to
  Aiken. So it is really meant as an interop format within the
  ecosystem.

crates/aiken/src/lib.rs

@@ -94,12 +94,12 @@ impl telemetry::EventListener for Terminal {
             telemetry::Event::WaitingForBuildDirLock => {
                 println!("{}", "Waiting for build directory lock ...".bold().purple());
             }
-            telemetry::Event::GeneratingUPLC { output_path, name } => {
+            telemetry::Event::GeneratingBlueprint { path } => {
                 println!(
-                    "{} {} in {}",
+                    "{} {} ({})",
                     "   Generating".bold().purple(),
-                    name.bold(),
-                    output_path.display().bright_blue()
+                    "contract blueprint".bold(),
+                    path.display().bright_blue()
                 );
             }
             telemetry::Event::GeneratingDocFiles { output_path } => {