QA-2282: Add app-version output

[ichengchang]

Ticket: QA-2282

Use the following logic to determine app versioning for contract tests
If the current commit hash for tag is the same as the current commit hash,

• app version of published contract = tag from bumper output, otherwise
• app version of published contract = new_tag from bumper output

---

PR checklist

• Include the JIRA issue number in the PR description and title
• Make sure Swagger is updated if API changes
  • ...and Orchestration's Swagger too!
• If you changed anything in model/, then you should publish a new official rawls-model and update rawls-model in Orchestration's dependencies.
• Get two thumbsworth of PR review
• Verify all tests go green, including CI tests
• Squash commits and merge to develop (branches are automatically deleted after merging)
• Inform other teams of any substantial changes via Slack and/or email

[calypsomatic]

Use the following logic to determine app versioning for contract tests If the current commit hash for tag is the same as the current commit hash,

This check happens in the bumper workflow?

[jyang-broad]

looks good! now compares tag + new-tag into app-version which is the "correct" version of pact contracts to test.

[ichengchang]

Use the following logic to determine app versioning for contract tests If the current commit hash for tag is the same as the current commit hash,

This check happens in the bumper workflow?

Yes this check happens in the bumper workflow, as shown below

https://github.com/DataBiosphere/github-actions/blob/master/actions/bumper/entrypoint.sh#L76-L88

# get current commit hash for tag
# on the initial use, this shows usage, because $tag is empty. The logic below still works.
tag_commit=$(git rev-list -n 1 $tag)

# get current commit hash
commit=$(git rev-parse HEAD)

if [ "$tag_commit" == "$commit" ]; then
    echo "No new commits since previous tag. Skipping..."
    echo tag=$tag >> $GITHUB_OUTPUT
    exit 0
fi