Feat: improved cargo shuttle version error

[jmwill86]

Small fix for helping to reduce any initial friction. On firing up a previous project I got the "unexpected end of input while parsing minor version number" due to an old "0.2" version on the shuttle-service. This merge request makes it clearer that the version error is related to the shuttle-service value in Cargo.toml.

Related to #213

[chesedo]

Suggested change

	let service_semver = match Version::parse(current_shuttle_version.as_str().unwrap()) {
	Ok(version) => version,
	Err(error) => return Err(anyhow!("Your shuttle-service version ({}) is invalid and should follow the MAJOR.MINOR.PATCH semantic versioning format. Error given: {:?}", current_shuttle_version.as_str().unwrap(), error.to_string())),
	};
	let service_semver = Version::parse(current_shuttle_version.as_str().unwrap())
	.map_err(|error| anyhow!(
	"Your shuttle-service version ({}) is invalid and should follow the MAJOR.MINOR.PATCH semantic versioning format. Error given: {:?}",
	current_shuttle_version.as_str().unwrap(),
	error.to_string()
	))?;

Another common why of structuring this. But a cargo fmt might be needed if you want to accept this suggestion.

[chesedo]

Btw, thanks for this @jmwill86!