Fuzzing harness generator should operate in a manner similar to cargo fuzz init: it should create a subfolder in your project that would already have a Cargo.toml and have everything ready to go.
Since currently some harnesses may not be generate correctly and may not compile, we do not want to take the cargo-fuzz approach of "one project with many binaries", but rather generate multiple independently compiled projects so that if one fails to compile, the rest can still function.