Comment 1 for bug 2049461

This should be simple. At the time these statuses are emitted, I believe we will have the type on hand.

Incidentally, we might as well change the messages for KVM brokerage at the same time.

$ ag 'Creating container'
provider/lxd/environ_broker.go
138: _ = statusCallback(status.Allocating, "Creating container", nil)

container/lxd/manager.go
123: _ = callback(status.Provisioning, "Creating container spec", nil)
126: _ = callback(status.ProvisioningError, fmt.Sprintf("Creating container spec: %v", err), nil)
130: _ = callback(status.Provisioning, "Creating container", nil)
133: _ = callback(status.ProvisioningError, fmt.Sprintf("Creating container: %v", err), nil)

container/kvm/kvm.go
168: _ = callback(status.ProvisioningError, fmt.Sprintf("Creating container: %v", err), nil)
239: _ = callback(status.Provisioning, "Creating container; it might take some time", nil)

$ ag 'Container started'
provider/lxd/environ_broker.go
143: _ = statusCallback(status.Running, "Container started", nil)

container/lxd/manager.go
136: _ = callback(status.Running, "Container started", nil)

container/kvm/kvm.go
257: _ = callback(status.Running, "Container started", nil)