Refresh versions (COMMUNITY)

[jmfayard]

Checklist

Thank you for this this PR! Please consider the following:

• To the Community ❤️:
  • Please link to an issue ticket where your code change has been greenlit, otherwise it's unlikely it can be merged.
  • Use a descriptive title: {task_name} (closes #{issue_number}), e.g.: Use logger (closes # 41).
  • If this PR comes from a fork, please Allow edits from maintainers
  • The PR can not contain changes in localization files, e.g. values-[LANGUAGE-CODE]/strings/* and / or assets/* (see #332 for further information).
• To the Maintainers ☕:
  • Title structure: Jira ticket name (EXPOSUREAPP-XXXX).
  • Set labels: maintainers, sprintX.
  • Update Jira status: In Review.
  • Fulfill internal Acceptance Criteria.
  • If mentioned in the Jira ticket link all corresponding GitHub issues in the sidebar.
• To everyone 🗺️:
  • Describe your changes in detail, if you changed the UI, screenshots or GIFs would be awesome!
  • Short step by step instructions help the reviewer test your changes, e.g. how to navigate to a new UI element you added.
  • The PR won't be reviewed if CircleCi is failing or if there are merge conflicts. If Circle CI is still failing mark the PR as a draft and write a little comment on your status.
  • Provide at least a few unit and/or instrumentation tests.
  • Use a meaningful branch name. Use either fix or feature as prefix for your branch, e.g. fix/prevent-npe-on-device-rotation-issue_123
  • Test your changes thoroughly. Only open PRs which you think is ready to be merged. If you explicitly need feedback mark the PR as DRAFT on GitHub.
  • Don't introduce unrelated code reformatting (e.g., on-save hooks in your IDE)
  • Remove this checklist before creating your pull request.

Description

Add gradle refreshVersions to make adding and updating dependencies easier

Steps to reproduce

• Run $ ./gradlew refreshVersions
• Edit the file versions.properties
• See https://jmfayard.github.io/refreshVersions/update-dependencies/

---

Internal Tracking ID: EXPOSUREAPP-7289

[dsarkar]

Internal Tracking ID: EXPOSUREAPP-7289

[d4rken]

Thanks for the PR, but we can't merge this:

• You didn't read the PR template?
• We generally only refresh libraries if there is a bugfix or feature we want.
• Just updating for the sake of it can introduce new bugs and requires additional testing effects to make sure the dependency upgrade did not break anything.
• Dependency upgrades can require additional changes in our internal pipeline, where newer versions have to be greenlight before being able to use them. So cost/benefit needs to be right for a dependency upgrade.
• This seems a bit like self advertisement for your refreshVersions plugin?