feat: local and remote trigger Java common SDK testing

[typotter]

🎟️ towards FF-3085
Ticket FF-3085

👯‍♂️ Related PRs

• sdk-common-jvm
• quality: First batch of Local and Remote SDK testing #57
• quality: Round 2 of SDK test workflow migrations #58
• Round 3 of workflow refactoring #59

Motivation

Changes are often made to the sdk-test-data repository to capture new behaviours, bugs and edge cases. When these changes are pushed to main, the SDKs are cloned locally (locally to the github action running) and their respective tests are run. These tests are set up and run by copies of the SDK test workflows - see sdk-test-data workflow. There are a number of limitations to this setup:

• Test steps are copied from the SDK’s respective workflows; changes to the SDK test workflows need to be replicated in sdk-test-data and this is not obvious to devs
• The SDK tests are not able to run against in-flight changes to sdk-test-data
• When new test-data is committed that breaks an SDK, that breakage is not surfaced in the SDK’s repository until some action triggers its testing workflow (on demand, on pull-request, etc.).

Description of Changes

• add java-common testing to the group!

Repos are green!

External to this Change
🚀 - Each SDK's testing workflow is enhanced into a reusable workflow, exposing parameters for SDK branch and the sdk-test-data branch to use in testing.

[aarsilv]

Looks good--will approve once tp/apibranch is merged and then purged from this PR 😛

[typotter]

temp refs removed! ptal!