Improve Clarity of PostgreSQL Upgrade Messages

What does this MR do?

This MR addresses the issues linked below that aim to improve the wording of the Checking if we already upgraded: NOT OK and Checking for previous failed upgrade attempts: NOT OK messages.

For the former, NOT OK, at the very least, indicates an expected status, and users have reported to cancel the migration after seeing this message.

For the latter, NOT OK is the desired status, indicating that no previous failed upgrade attempts were found. This is extremely confusing, and has been instead changed to NONE FOUND (in green) or FAILURE DETECTED (in red) if a previous failed upgrade was found, followed by the file path.

Related issues

1. Closes #4572
2. Closes #9135

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• Latest Merge Result pipeline is green.
• When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
• If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
• If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created/updated.
• Tests added.
• Integration tests added to GitLab QA.
• Equivalent MR/issue for the GitLab Chart opened.
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.