Repository: stable-diffusion-webui
Issue: [Bug]: minor bug in the total progress
Labels: bug-report

### Checklist

- [x] The issue exists after disabling all extensions
- [x] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [x] The issue exists in the current version of the webui
- [x] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

in img2img the total progress reflects the progress that would happen only if one enforces to use all the steps, as img2img usually skips most of them.

### Steps to reproduce the problem

1. go to img2img.
2. create a job doing all the passages you want.
3. check the command-line for the progress.
4. notice how it wrongfully reports a much higher number of steps required. Which would be correct if this was not img2img

### What should have happened?

WebUI should check if the "With img2img, do exactly the amount of steps the slider specifies." setting is pressed beore calculating how much time and steps are left in the total for the job.

### What browsers do you use to access the UI ?

Google Chrome

### Sysinfo

[sysinfo-2024-01-17-05-03.json](https://github.com/AUTOMATIC1111/stable-diffusion-webui/files/13958820/sysinfo-2024-01-17-05-03.json)


### Console logs

```Shell
Loading weights [4199bcdd14] from D:\Documents\GitHub\stable-diffusion-webui\models\Stable-diffusion\Rev Animated V1.2.2.safetensors
Applying attention optimization: xformers... done.
Weights loaded in 3.6s (send model to cpu: 1.2s, load weights from disk: 0.2s, apply weights to model: 0.8s, move model to device: 1.3s).
100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 76/76 [01:06<00:00,  1.14it/s]
Reusing loaded model Rev Animated V1.2.2.safetensors [4199bcdd14] to load Lyriel V1.6.safetensors [ec6f68ea63]██████████████████████████████████████████████████████████████████████████████████████████████▏                                                         | 608/800 [11:15<02:43,  1.17it/s]
Loading weights [ec6f68ea63] from D:\Documents\GitHub\stable-diffusion-webui\models\Stable-diffusion\Lyriel V1.6.safetensors
Applying attention optimization: xformers... done.
Weights loaded in 3.3s (send model to cpu: 1.0s, load weights from disk: 0.2s, apply weights to model: 0.6s, move model to device: 1.3s).
*** Error adding [generation_number] to filename
    Traceback (most recent call last):
      File "D:\Documents\GitHub\stable-diffusion-webui\modules\images.py", line 484, in apply
        replacement = fun(self, *pattern_args)
      File "D:\Documents\GitHub\stable-diffusion-webui\modules\images.py", line 367, in <lambda>
        'generation_number': lambda self: NOTHING_AND_SKIP_PREVIOUS_TEXT if (self.p.n_iter == 1 and self.p.batch_size == 1) or self.zip else self.p.iteration * self.p.batch_size + self.p.batch_index + 1,
    AttributeError: 'Processed' object has no attribute 'n_iter'

---
Total progress:  76%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏                                                         | 608/800 [11:27<03:37,  1.13s/it]
X/Y/Z plot will create 8 images on 1 1x8 grid. (Total steps to process: 800)████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏                                                         | 608/800 [11:27<02:43,  1.17it/s]
```


### Additional information

For some idiotic reason i added "generation number" to the archive filename. That is my personal mistake here. Not a bug. Nor the bug i am complaining about. I asked it to generate images cycling models with 100 steps per image and using a img2img, it decided to use 76 steps per image as it needed less denoising, but the total job still lists 800 total steps needed which would be true (8 models for 100 steps each image) if this was not img2img and thus less denoising is required.