Replace indiesdev/[email protected] action

[Ponnia-M]

What was the problem?[^1]

Multiple warnings with indiesdev/[email protected] action in our pipelines:

• The following actions uses node12 which is deprecated and will be forced to run on node16: indiesdev/[email protected].
• The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Github Actions workflows affected by warnings above:

1. Continuous Integration (CI) => 26 warnings across various jobs
2. CI: API Gateway integration test => 10 warnings (mostly deprecated 'set-output' command)
3. CI: BIE Kafka End-2-End Test => 2 warnings
4. CI: EE - EP Merge - Integration Test => 4 warnings
5. CI: SVC BGS API integration test => 9 warnings
6. CI: SVC BIP API integration test => 2 warnings
7. Secrel => 6 warnings

Associated tickets or Slack threads:

• Track Github action and its warnings #2721

How does this fix it?[^1]

Created a new action found in a public VA repo

How to test this PR

• Run the affected workflows with my branch (update-action/ponnia) and errors related to this action don't pop up anymore.
• Secrel => For clarity, all indiesdev/[email protected] action warnings in our Secrel workflow have been resolved. However, the current node.js 16 warnings seen here are from another action (see picture below). Based on this conversation reverting back to v5 brought back these errors.

[github-actions]

Test Results

151 tests  ±0   151 ✅ ±0   47s ⏱️ ±0s
 46 suites ±0     0 💤 ±0 
 46 files   ±0     0 ❌ ±0 

Results for commit 5960410. ± Comparison against base commit 6d22e47.

♻️ This comment has been updated with latest results.

[github-actions]

JaCoCo Test Coverage

Overall Project	76.63%	❌

There is no coverage information present for the Files changed

[tejans24]

Adding comments

[Ponnia-M]

@tejans24 @cheng PR has been updated and curl-action is now in public VA repo. Testing was successful for affected workflows.

[chengjie8]

LGTM