Enable manual workflow trigger

[sunilkumardash9]

Description of changes

Summarize the changes made by this PR.

• Added a workflow_dispatch to manually trigger test workflows
• will be good for development experience

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readbility, Modularity, Intuitiveness)

[jeffchuber]

@tazarov can you take a look at this?

[HammadB]

How does workflow dispatch work for unauthorized users

[tazarov]

@HammadB @jeffchuber

Here's the 1 min read - https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow#configuring-a-workflow-to-run-manually

The gist:

To trigger a workflow in a repository, the user should be a collaborator with Write permission in the repository. Normally the external users can’t trigger workflows in the repository.

Ref: https://github.com/orgs/community/discussions/26053#discussioncomment-3250202

[tazarov]

I think this can be useful.

On a side note: I am unsure whether this can be triggered on a PR branch - useful for some preliminary tests before doing the full 360.

[sunilkumardash9]

@tazarov The idea behind this is to run unit and integration tests on a forked repository manually. This could help anyone pushing changes to manually check if changes are passing checks before making PRs or testing existing PR branches without needing maintainers to approve them after every fix.

[tazarov]

@tazarov The idea behind this is to run unit and integration tests on a forked repository manually. This could help anyone pushing changes to manually check if changes are passing checks before making PRs or testing existing PR branches without needing maintainers to approve them after every fix.

@sunilkumardash9, thanks for the clarification. I guess provided one enables GH Actions on a forked repo that should be possible, yes :)

[HammadB]

Looks great! Thanks!

[HammadB]

You'll have to rebase on #1054

[tazarov]

@sunilkumardash9, your rebase did not work. Can you do it again?

[sunilkumardash9]

@tazarov It should be passing now.

[HammadB]

@sunilkumardash9 thanks for the add