fix: Nixopus self-host UI does not update with latest GitHub commit even though build logs refresh

[Sumabhat11]

Description
When new commits are pushed to the connected GitHub repository, the Nixopus self-hosted instance does not display the updated code changes in the project interface or code view. However, the Log Viewer correctly reflects the new commit information, indicating that the GitHub webhook and build trigger are functioning, but the UI synchronization is not.

---

To Reproduce
Steps to reproduce the behavior:

1. Log in to the Nixopus using the admin account.
2. From the left-hand menu, navigate to Self Host → Application.
3. Select the application linked to a GitHub repository.
4. Open the Logs tab to view the build logs.
5. Push a new commit to the connected GitHub repository (e.g., on the main branch).
6. Observe that:
   • The Log Viewer updates with the new build details.
   • The Application Interface in Nixopus does not update to reflect the latest commit.
7. Attempting a manual refresh or using the Fetch More / Refresh buttons does not resolve the issue.

---

Expected behavior
After pushing new commits to the connected GitHub repository, Nixopus should automatically refresh the project’s code view to display the latest version corresponding to the most recent commit.

---

Additional context

• Issue occurs on self-hosted Nixopus instance.
• GitHub integration is authorized with access to all repositories.
• Browser console shows no visible errors.
  -Indicates that the GitHub webhook and synchronization pipeline are partially functional.

[linear]

NIX-162