METRON-1372 Validate JIRA for Releases

[nickwallen]

Adds a script that helps the Release Manager validate JIRA for a pending release.

Help is printed along with an example.

$ ./release-utils/validate-jira-for-release --help

usage: ./release-utils/validate-jira-for-release
    -v/--version=<version>   The version of the next release. [Required]
    -s/--start=<start>       Defines the first commit to inspect. [Required]
    -e/--end=<end>           Defines the last commit to inspect.
    -r/--repo=<repo>         The Git repo to work from.
    -b/--branch=<branch>     The branch to work from.
    -h/--help                Usage information.

example:
    validate-jira-for-release --version=0.4.2 --start=tags/apache-metron-0.4.1-release

Validating the next release.

$ ./release-utils/validate-jira-for-release --version=0.4.2 --start=tags/apache-metron-0.4.1-release
Cloning into 'metron-0.4.2'...
remote: Counting objects: 35046, done.
remote: Compressing objects: 100% (13698/13698), done.
remote: Total 35046 (delta 15702), reused 31650 (delta 12822)
Receiving objects: 100% (35046/35046), 53.06 MiB | 6.77 MiB/s, done.
Resolving deltas: 100% (15702/15702), done.
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
Fetching origin
           JIRA          STATUS     FIX VERSION                       ASSIGNEE                                                FIX
    METRON-1345            Done                              Michael Miklavcic  https://issues.apache.org/jira/browse/METRON-1345
    METRON-1349            Done        Next + 1                     Nick Allen  https://issues.apache.org/jira/browse/METRON-1349
    METRON-1343            Done                                          Mohan  https://issues.apache.org/jira/browse/METRON-1343
    METRON-1306           To Do                                     Unassigned  
...

Pull Request Checklist

• Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
• Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
• Has your PR been rebased against the latest commit within the target branch (typically master)?
• Have you included steps to reproduce the behavior or problem that is being changed or addressed?
• Have you included steps or a guide to how the change may be verified and tested manually?
• Have you ensured that the full suite of tests and checks have been executed in the root metron
• Have you written or updated unit tests and or integration tests to verify your changes?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

[ottobackwards]

can we make the work dir ~/tmp like the other scripts?

[nickwallen]

Sure, done.

[ottobackwards]

+1 worked great