af/init command

[cacama-valvata]

Opening a premature PR on this so that I can get midway feedback and get most of my "TODO" questions answered this Sunday (not all of the TODOs are for y'all but most of them are, feel free to comment on any you want to give insight on). Please add your answers to the TODOs via comments in a review on this PR since I can't be there this Sunday

[cacama-valvata]

clarification: i do not care about code formatting feedback, such as the compiler warnings for the structs or the cargo fmt fails. I will deal with those after all implementation is done.

[detjensrobert]

Structure comments:

• So far, I've tried to keep the bulk of the logic for comands in their own folders, and run() orchestrates which thing to call based on the command line flags (i.e. build::run() calls build_image() and then push_images() if --push was given). I think the *_init() functions and the struct definitions should go in their own folder/file to follow this. Thoughts from the rest of the team?

[cacama-valvata]

Structure comments:

* So far, I've tried to keep the bulk of the logic for comands in their own folders, and `run()` orchestrates which thing to call based on the command line flags (i.e. `build::run()` calls build_image() and then push_images() if `--push` was given). I think the `*_init()` functions and the struct definitions should go in their own folder/file to follow this. Thoughts from the rest of the team?

done

[cacama-valvata]

Since this PR is so out of date with the main branch, I have moved all of these changes to branch af/init-command2. Once that other branch is merged in, I will close this PR.