Better logging for init

[alenkacz]

What this PR does / why we need it:
Right now when you run init and you're initializing the server side as well as local environment, the only thing the command prints out is that local was initialized. This PR adds more logging to make it obvious that server side is being initialized as well.

This is output of init before this change

➜  kudo git:(av/maintainers-array) ✗ ./bin/kubectl-kudo init
$KUDO_HOME has been configured at /Users/alenavarkockova/.kudo

After

➜  kudo git:(av/init-logging) ✗ ./bin/kubectl-kudo init
$KUDO_HOME has been configured at /Users/alenavarkockova/.kudo
✅ installing crds
✅ preparing service accounts and other requirements for controller to run
✅ installing kudo controller

[zen-dog]

We desperately need fancy Unicode characters in the output! And not only here, but when installing instances too! And in the plan status output! Let the ✓ be an inspiration to you ;)

[zen-dog]

Now, that I think about it, it should be the other way around ;)

Suggested change

	clog.Printf("✓ installing crds")
	if err := installCrds(client.ExtClient); err != nil {
	return err
	}
	if err := installCrds(client.ExtClient); err != nil {
	return fmt.Errorf("❌failed to install CRDs: %w", err)
	}
	clog.Printf("✅ installed crds")

[zen-dog]

and the others too ;)

[kensipe]

I prefer @zen-dog graphics... and I do not like graphics in the error messages

[alenkacz]

🤔 so do we want to add the cross there or not? I am not sure I understand the conclusion of that sentence

[kensipe]

personally I prefer a more quiet cli... I really preferred the verbosity at 4 rather than at 0. I do like the unicode chars!

[zen-dog]

Unicode ftw!

[alenkacz]

I actually find it weird to run a command and have no feedback on what actually happened and if something happened. I think Zain or some of the SEs complained about it as well (that they don't have any feedback after the command is run). So I think we need to have at least a very short output for every command

[kensipe]

some additional thoughts...
the example output is now:

$KUDO_HOME has been configured at /Users/alenavarkockova/.kudo
installing crds
installing prereqs
installing kudo controller

when verbosity was 4... these were debugging messages to help potentially diagnose an issue. now at verbosity of 0 they are standard cli output... because of that... if we keep verbosity at 0 I think:

1. we need to case correctly... like CRDs and KUDO
2. I'm questioning abbrev... "prereq" has multiple issues... for one we should spell it out.. but it also begs the question what is that.

[gerred]

I don't have a strong opinion here. I do agree with @kensipe that we should expand the pronunciation and make those for humans.

I do like longer error messages that are more descriptive and try to help people in general. See Elm and Rust's errors for where I'm thinking there - obviously this is not that PR. IMO, Everything at log level 0 / printed by default should be non-expert human oriented and verbosity levels of that should be written for developers and experts.

[alenkacz]

@gerred @kensipe I updated the description with the current output, are we fine with it? I like it 😊

[alenkacz]

I am going to merge this. We can always iterate on master