Remove requirement to set up dylib

[lee-orr]

Setting up a crate as a dylib can break compilation in certain situations when it's not actually used as a dylib, especially on windows - leading to a "too many symbols" error. In Crossroad Blues I worked around it by creating a separate crate that was a dylib, and imported the game crate which only existed as an rlib.

For the CLI, it would be useful if we could avoid the need for that extra crate.

[lee-orr]

The solution I had set up doesn't work well with cross-compilation, so I'm going to aim for a different solution - possibly adding a "setup" command that sets up the extra crate and stuff like that....

[lee-orr]

Rather than changing the behavior here - I will adjust the docs, since I want to give users control of the structure of their projects as much as possible

[lee-orr]

Found a different solution by creating a temporary Cargo.toml with dylib when compiling/running via the CLI, and reverting to the original when the run is done. This prevents the compilation issues that can occur when you have dylib set on the crate but not used as part of the compilation itself...