[WebUI] Fix 'Use All' Params not Respecting Hi-Res Fix

[blhook]

This is a different source/base branch from #2823 but is otherwise the same content. yarn build was ran on this clean branch.

What was the problem/requirement? (What/Why)

As part of a change in 2.3.0, the high resolution fix was no longer being applied when 'Use all' was selected. This effectively meant that users had to manually analyze images to ensure that the parameters were set to match.
Additionally, and never actually working, Upscaling and Face Restoration parameters were also not pulling through with the action, causing a similar usability issue. See: #2823 (comment)

What was the solution? (How)

This change adds a new reducer to the postprocessingSlice file, mimicking the generationSlice reducer to assign all parameters appropriate for the post processing options. This reducer assigns:

• Hi-res's toggle button only if the type is txt2img, since img2img hi-res was removed previously
• Upscaling's toggle button, scale, denoising strength, and upscale strength
• Face Restoration's toggle button, type, strength, and fidelity (if present/applicable)

Minor

• Added endOfLine: 'crlf' to prettier's config to prevent all files from being checked out on Windows due to difference of line endings (and git not picking up those changes as modifications, causing ghost modified files from Git)

Revision 2:

• Removed out upscaling and face restoration pulling of parameters

Revision 3:

• More defensive coding for the hires_fix not present (assume false)

Out of Scope

• Hi-res strength (applied as img2img strength in the initial image that is generated) is not in the metadata of the final image and can't be reconstructed easily
• Upscaling and face restoration have some peculiarities for multi-post processing outside of the UI, which complicates it enough to scope out of this PR.

How were these changes tested?

• yarn dev => Server started successfully
• Manual testing on the development server to ensure parameters pulled correctly
• yarn build => Success

Notes

As with generationSlice, this code assumes action.payload.image is valid and doesn't do a formal check on it to ensure it is valid.

[psychedelicious]

Thanks for redoing this PR. I've requested two changes.

[lstein]

This looks good to me, pending the changes requested by @psychedelicious

[psychedelicious]

@blhook is this ready for review? Sorry if I missed a notification.

[blhook]

@psychedelicious , yes, it should be ready. I probably should have made a specific comment for it after the push (which was not too long after my replies to the conversation).

[psychedelicious]

Ah, good. I'll do my review this evening.

[psychedelicious]

All good, thank @blhook !