feat(next_version): support configuration

[orhun]

This PR makes it possible to configure the next_version crate to customize the behavior for cases like orhun/git-cliff#343

e.g.:

let next_version = semver
	.next(
		vec![],
		Some(NextVersionConfig {
			uncontrolled_minor_bump: false,
			initial_major_increment: false,
		}),
	)
	.to_string();

A couple of points:

• This is a breaking change due to the newly added config parameter to the next function. Let me know if you are fine with it or not and we can probably think of a way to make it non-breaking. I think it is fine though.
• I'm not sure about the names of the config variables.
• I tried this out with git-cliff directly and it seems to work as expected. However, I must say it was really hard to wrap my head around the conditions so I might have missed something. Please double check.

🐻

[MarcoIeni]

I would prefer a non-breaking change. Let's keep the default behavior as it is.
Let's create another struct and use the builder pattern to configure it.
I will write an example now.

[orhun]

Added tests.

[MarcoIeni]

struct VersionUpdater {
    pub uncontrolled_minor_bump: bool,
    pub initial_major_increment: bool,
}

impl VersionUpdater {
    // builder lite pattern https://matklad.github.io/2022/05/29/builder-lite.html
    fn with_uncontrolled_minor_bump(mut self, uncontrolled_minor_bump) -> Self { self.uncontrolled_minor_bump = uncontrolled_minor_bump; self }
    
    fn next(&self, version: Version, commits: I) -> Version { }
}

Then Version::next calls VersionUpdater with the default options.

[orhun]

I didn't get it, do you wanna define another struct called VersionUpdater and have the configuration values there? How about config::NextVersionConfig?

[MarcoIeni]

do you wanna define another struct called VersionUpdater and have the configuration values there?

yes

How about config::NextVersionConfig?

Let's delete it. The VersionUpdater has the default configuration, which you can override with the builder pattern.

[orhun]

Sorry, I'm not following. Do you want to achieve the following API?

let next_version = semver
	.next(
		vec![]
	)
    .with_uncontrolled_minor_bump(true)
    .with_initial_major_increment(true)
	.to_string();

[orhun]

Or is it something like this?

VersionUpdater::new(semver)
    .with_uncontrolled_minor_bump(true)
    .with_initial_major_increment(true)
    .next(vec![])

[MarcoIeni]

VersionUpdater::new()
    .with_uncontrolled_minor_bump(true)
    .with_initial_major_increment(true)
    .next(semver, vec![])

I was thinking this what do you think?

[orhun]

Sure, makes sense. Implemented in d3d3fb0