blueprint: move pipeline generation into its own package

Introduce the `distro` package, which contains an interface for OS
implementations. Its main purpose is to convert a blueprint to a
distro-specific pipeline.

Also introduce the `distro/fedora30` package. It is the first
implementation of the distro interface. Most of its code has been copied
with minimal modifications from the blueprint package.

The `blueprint` package is now back to serving a single purpose:
representing a weldr blueprint. It does not depend on the `pipeline`
package anymore.

Change osbuild-composer and osbuild-pipeline to use the new API,
hard-coding "fedora-30". This looks a bit weird now, but is the same
behavior as before.

All test cases now also take an "distro" key in the "compose" object.

test/cases/ami_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "filename": "image.ami",
     "output-format": "ami",
     "blueprint": {}

test/cases/disk_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "output-format": "partitioned-disk",
     "filename": "disk.img",
     "blueprint": {}

test/cases/ext4_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "output-format": "ext4-filesystem",
     "filename": "filesystem.img",
     "blueprint": {}

test/cases/openstack_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "output-format": "openstack",
     "filename": "image.qcow2",
     "blueprint": {}

test/cases/qcow2_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "output-format": "qcow2",
     "filename": "image.qcow2",
     "blueprint": {}

test/cases/vhd_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "output-format": "vhd",
     "filename": "image.vhd",
     "blueprint": {}

test/cases/vmdk_empty_blueprint.json

@@ -1,5 +1,6 @@
 {
   "compose": {
+    "distro": "fedora-30",
     "output-format": "vmdk",
     "filename": "disk.vmdk",
     "blueprint": {}