New branch policy configuration parameter to control at which tag to stop

Now the plugin uses the first tag it finds in the log history.
Maybe a new configuration for the branch policy could be added so that this behavior could be changed.
This is useful in cases when release branches are used. Because the annotated tags will be on release branches and the lightweight tags on master, after merges the lightweight tag on master might need to be moved. This means more work to move the tag and also all local repositories need to update the tag as well.

Suggestion: stop on tag:

- first (default) - current behavior

- first annotated tag

- first lightweight tag

This way we could configure the release branches to stop on first annotated tag and the master on first lightweight tag.