T7981: conflict check workflow updated to support schedule and workflow dispatch

[kumvijaya]

Change Summary

PR Conflict Check Workflow - Updated for Scheduled Execution

Enhanced the PR conflict checking workflow to support scheduled and manual triggers, addressing the issue where GitHub's mergeable state is unreliable immediately after commits.

The scheduled approach will help to solve the issue where immediate post-commit checks don't provide accurate merge status, ensuring comprehensive and reliable conflict detection.

Note:
Corresponding caller workflows will be added in subsequent PRs, with both schedule and workflow-dispatch triggers.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, renaming)
• Refactoring (no functional changes)
• Other (please describe):

Related Task(s)

Related PR(s)

Proposed changes

How to test

Checklist:

• I have read the CONTRIBUTING document
• I have linked this PR to one or more Phabricator Task(s)
• My commit headlines contain a valid Task id
• My change requires a change to the documentation
• I have updated the documentation accordingly

[dmbaturin]

I have reservations about scripts embedded in YAML. They are hard to execute and debug separately, or run through linters and other tools. Can we move it to a file and call it from there?

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[kumvijaya]

I have reservations about scripts embedded in YAML. They are hard to execute and debug separately, or run through linters and other tools. Can we move it to a file and call it from there?

@dmbaturin Created typescript (js) action and script code taken out from workflow

[sever-sever]

Can you squash 23 commits to some logical sequence?
There’re should be either 1 commit or some logical separation like ;

• update flow, use xxx instead of xxy
• Use JS for xxx
• Use TS for xxx

otherwise it will be not good for commit history

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[kumvijaya]

Can you squash 23 commits to some logical sequence? There’re should be either 1 commit or some logical separation like ;

• update flow, use xxx instead of xxy
• Use JS for xxx
• Use TS for xxx

otherwise it will be not good for commit history

Done