v0.7.3 - Hotfix: Deploy from Dockerfile build status polling

Main Changes

• Fixed false "Build failed" notification in Deploy from Dockerfile: the background polling that checks the Kaniko build Job status could lose its authenticated context. AsyncTasks.schedulePolling dispatched each recurring tick through DelegatingSecurityContextExecutor.execute(...) called by the shared clock thread, which never has an authenticated user — this made Kubernetes credential resolution fail mid-poll (Unable to resolve Kubernetes credentials: no authenticated user), aborting the status check and reporting a failure even when the Kaniko Job had completed successfully and the image was already pushed to the registry.
• Isolated build log fetching from status checking: DeployFromDockerfileView now reads the build pod's logs in its own try/catch, so a transient log-read failure (e.g. a short-lived Kaniko container tearing down) no longer aborts the real Job status check.

Impact

This fixes every view that relies on AsyncTasks.schedulePolling for recurring background checks: BuildLogsView, DeployFromDockerfileView, ImportComposeView, MainLayout, and PodLogsView.