HPCC-32168 Add Dynamic ECL-Bundles Listing Feature for Bundle Testing…

[Charan-Sharan]

Add Dynamic ECL-Bundles Listing Feature for Bundle Testing Action File.
This code adds a dynamic feature to list the ecl-bundles list from the hpcc-systems/ecl-bundles repository. Adding this feature removes the need to manually updated the bundles list when a new bundle is added.

Type of change:

• This change is a bug fix (non-breaking change which fixes an issue).
• This change is a new feature (non-breaking change which adds functionality).
• This change improves the code (refactor or other change that does not change the functionality)
• This change fixes warnings (the fix does not alter the functionality or the generated code)
• This change is a breaking change (fix or feature that will cause existing behavior to change).
• This change alters the query API (existing queries will have to be recompiled)

Checklist:

• My code follows the code style of this project.
  • My code does not create any new warnings from compiler, build system, or lint.
• The commit message is properly formatted and free of typos.
  • The commit message title makes sense in a changelog, by itself.
  • The commit is signed.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly, or...
  • I have created a JIRA ticket to update the documentation.
  • Any new interfaces or exported functions are appropriately commented.
• I have read the CONTRIBUTORS document.
• The change has been fully tested:
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have checked that this change does not introduce memory leaks.
  • I have used Valgrind or similar tools to check for potential issues.
• I have given due consideration to all of the following potential concerns:
  • Scalability
  • Performance
  • Security
  • Thread-safety
  • Cloud-compatibility
  • Premature optimization
  • Existing deployed queries will not be broken
  • This change fixes the problem, not just the symptom
  • The target branch of this pull request is appropriate for such a change.
• There are no similar instances of the same problem that should be addressed
  • I have addressed them here
  • I have raised JIRA issues to address them separately
• This is a user interface / front-end modification
  • I have tested my changes in multiple modern browsers
  • The component(s) render as expected

Smoketest:

• Send notifications about my Pull Request position in Smoketest queue.
• Test my draft Pull Request.

Testing:

[github-actions]

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-32168

Jirabot Action Result:
Workflow Transition: Merge Pending
Updated PR
Assigning user:

[AttilaVamos]

Seems good, but there are 2 questions.

[AttilaVamos]

What happens if no README.rst?

[Charan-Sharan]

I will add condition to check if README.rst file is present. So that it won't fail the workflow file for not having a README.rst file.

[AttilaVamos]

The sort command already has a -u or --unique parameter. Is that suitable here?

[Charan-Sharan]

Oh! Yes, the sort command has a -u parameter, it would be suitable here and we can eliminate uniq command.

[Michael-Gardner]

If your way works, and you're happy with it, that's fine. I added a different way to write out a block of code. I personally think it's a bit cleaner. You will see the cat redirect EOF style used in a lot of bash code

[AttilaVamos]

Seems good.

[Charan-Sharan]

@ghalliday could you please merge this PR?