fix exit codes of binaries

[marcoow]

This fixes the exit codes of the project binaries that currently swallow any errors (they log the errors but always return a successful exit code. That's not critical when working with the binaries in development but leads to bugs like #169 going unnoticed in CI…

The code is quite repetitive now and could use some cleanup eventually.

This also fixes 2 actual errors in the generators which fix CI (which now correctly fails because of these errors).

closes #169

[LukeMathWalker]

I'm not super fond of the pattern here, where we log the error manually in every single place.
I think it'd be more robust to do this logging in the main function above, before exiting with a non-zero code.

I imagine this was originally done to control the message shown to the user. We can achieve the same goal with the following structure:

Suggested change

	match reset(&mut ui, &config.database).await {
	Ok(db_name) => {
	ui.outdent();
	ui.success(&format!("Reset database {} successfully.", db_name));
	Ok(())
	}
	Err(e) => {
	ui.outdent();
	ui.error("Could not reset database!", &e);
	Err(e)
	}
	}
	let outcome = reset(&mut ui, &config.database).await.context("Could not reset the database!");
	ui.outdent();
	let db_name = outcome?;
	ui.success(&format!("Reset database {} successfully.", db_name));
	Ok(())

and in main:

 match cli().await {
        Ok(_) => ExitCode::SUCCESS,
        Err(e) => {
            ui.error(e.to_string(), &e);
            ExitCode::FAILURE,
        }
    }

[LukeMathWalker]

Ideally ui.error would just take the error, relying on its Display implementation, rather than forcing the caller to invoke e.to_string(), but that can be fixed later.