Report Abort job failure via DaemonResult=Failed condition

**Epic:** #1080

Add a new failure reason constant `ReasonDaemonCustomJobFailed` (alongside existing `ReasonDaemonFileDownloadFailed`, etc. in `networkupgrade_common_types.go` in solo-operator). When `RunPhaseJobs` returns an Abort error in the daemon, set:

```
DaemonResult=Failed
Reason=ReasonDaemonCustomJobFailed
Message=:
```

## Acceptance Criteria
- [ ] New reason constant added to `networkupgrade_common_types.go` in solo-operator
- [ ] Daemon sets the condition correctly on Abort failure
- [ ] Existing DaemonResult success path is unaffected

Start by reading networkupgrade_common_types.go for the existing daemon failure reasons, then trace the daemon entry point where RunPhaseJobs handles an Abort error. Confirm that the new reason and DaemonResult=Failed condition use the job descriptor stem and exit code, while the existing success path remains unchanged.

Written by the indexing model from the issue text.