jenkins job: research oddities with merge, stages run, status, etc.

Patch: https://gerrit.opencord.org/c/voltha-openonu-adapter-go/+/34777

Repo: voltha-openonu-adapter-go

Flow:

• patch upload
• edits for Mahir(s) review comments
• commit msg edits for Jan(s) review comments
• success reported
• mahir & serkant add +1
• My commenting on patch cleared the approvals and +1 verify.
• Manually re-added attributes.
• rebase-with-master to resolve merge conflicts.
• Re-add attributes twice due to interim patch comments clearing attributes.

Oddity #1

• Job passed then later failed version check during merge.
• Job that ran post rebase should have failed due to tag check (last patch merged was 2 weeks ago).

Oddity #2

• Job failure was reported in email as a patch status.
• https://jenkins.opencord.org/job/version-tag_wildcard/490/console
• This failure was not logged in the patch history, was the job re-run and succeded on the 2nd attempt ?  ( ie bad dependencies somewhere short-circuited running the test or reacting to status ).

Oddity #3

• Failing patch was reverted (click on revert link in gerrit, top right).
• Patch status 'Apply' was displayed for a short time in gerrit.
• After the revert patch job succeeded patch status changed again to 'merged'.
• This status is incorrect, 'merged' applied to a reverted patch will essentially merge the submitted patch out of existence.  Edits cannot be applied to the existing patch in gerrit due to the merged status.