Optimize CI/CD workflows by excluding redundant CI runs on direct master pushes

[origranot]

Description

Currently, our development process triggers both Continuous Integration (CI) and Deployment (CD) workflows when new code is pushed to the master branch.
While this is crucial for maintaining code quality and ensuring reliable deployment, it has been observed that running the CI workflow for direct pushes to the master branch may be redundant.
This is especially true if the code has already passed through the CI checks in a separate development or feature branch before merging.

Screenshots

No response

Additional information

Outcome:

• Optimize the CI/CD process by configuring the pipeline to intelligently skip the CI workflow for direct pushes to the master branch, where it's confirmed that the code has already passed CI checks.
• Ensure that this optimization does not compromise the integrity and reliability of the code in the master branch.
• Maintain or improve the current deployment speed and resource efficiency.