Enhance deploy and rollback forms with improved target handling

[egasa21]

This pull request improves the deploy history UI and optimizes the deploy execution process, especially for Talos builds. The main changes include skipping image pulls for locally built images, refining how deploy events are loaded and displayed, and updating the HTML structure to better handle deploy history updates and empty states.

Backend improvements:

• The Engine.execute method now takes a skipPull parameter to optionally skip pulling the Docker image if it was just built locally (e.g., by Talos), improving deploy efficiency. [1] [2] [3]

Frontend/UI improvements:

• Deploy event rows are now loaded on demand (via click) for completed deploys, and auto-loaded (and refreshed every 2s) for running or pending deploys. The click-to-load behavior is handled by a new toggleDeployEvents JavaScript function, and the corresponding HTML in deploy_row.html is updated for this logic. [1] [2] [3]
• The deploy history table now uses a new anchor element (#deploy-history-anchor) for HTMX swaps, and empty state handling is improved to remove the "No deploys yet" message after the first deploy. [1] [2] [3] [4]

These changes make the deploy process more efficient for Talos builds and provide a more responsive and user-friendly deploy history UI.… and event loading