Add feature to allow specifying version upgrade type on arguments list.

[esequielvirtuoso]

What?

Add feature to allow specifying version upgrade type on arguments list.

Type of change?

• [breaking change(s)]: Changes that will require other changes in dependant applications.
• [build]: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• [ci]: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• [docs]: Documentation only changes
• [feat]: A new feature
• [fix]: A bug fix
• [perf]: A code change that improves performance
• [refactor]: A code change that neither fixes a bug nor adds a feature
• [style]: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• [test]: Adding missing tests or correcting existing tests

Note: Remove the non-checked options

Why?

We need a way to make semantic release easier.

How?

By adding a new feature to allow user to specify upgrade type (major, minor, patch).

How has this been tested?

• Unit tests
• Integration tests
• Benchmark tests

Before submitting a PR please make sure to check if:

• The code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• The changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and/or existing unit tests pass locally with my changes
• New and/or existing integration tests pass locally with my changes