Create warning event when postgres version is EOL.

[dsessler7]

Checklist:

• Have you added an explanation of what your changes do and why you'd like them to be included?
• Have you updated or added documentation for the change, as applicable?
• Have you tested your changes on all related environments with successful results, as applicable?
  • Have you added automated tests?

Type of Changes:

• New feature
• Bug fix
• Documentation
• Testing enhancement
• Other

What is the current behavior (link to any open issues here)?

When a user has a postgrescluster that is using an End-Of-Life version of postgres, we don't warn them.

What is the new behavior (if this is a feature change)?

• Breaking change (fix or feature that would cause existing functionality to change)

We add a warning event to the postgrescluster if the postgres version is End-Of-Life.

Other Information:

[cbandy]

The implementation looks good. I'll let others comment on the warning reason or text.

[cbandy]

One last pile of nitpicks about formatting messages. LGTM