Move the "sample project generating" from "after merging new PRs into develop" to "directly refreshing the updates on each PR"

[luongvo]

Issue

Currently, there is a workflow to generate and update the sample project for referencing. The idea is after merging a new PR into develop branch, the workflow will be triggered on the merge commit to generate the sample project, commit and push all new changes. This initial approach works properly as it is, however, it has come cons as below:

• We MUST add bot-nimble account to Allow specified actors to bypass required pull requests to push new commits directly to the develop branch (Fix: generating sample project is failing to push changes to develop (protected branch) #210), that kindly not a normal process.
• We MUST check and make sure to run the workflow only on the merge commit to save CI resources (Improve: skip git push action if there are no changes from the sample project #212).
• We SHOULD consider not executing some CD workflows to test the development process on [Chore] Generate & update sample project commit.
• We can not review all the final generated-project (sample) after making some changes in the template structure on a PR 🤔

Solution

So, instead of generating & updating the sample project after merging new PRs into the develop, we can do it directly on each PR. That means, after making and pushing some changes in the template structure into a PR, there is a new workflow that will generate and push a new commit directly into that PR to show the new updates for the sample project.

This approach has some concerns are:

• Pushing a new commit via a bot account after a commit from the author will cause the author can not push new commits without pulling or force-pushing 👉 Since, the bot pushes the new commits to update the project, the author can ignore those and force-push new update commits into their PRs. The bot will push new commits afterward by combining all the changes in the final sample project ✅
• The bot will not push an update commit without changes ✅
• We can review both all changes from the template structure (by Mason) and the generated project result (sample) at the same time in one PR ✅

Who Benefits?

Developers

What's Next?

• Involve the team in the final agreement.
• Prepare new tasks to migrate the existing workflow to the new workflow to be executed on each PR.

[luongvo]

Ticket is created #255