Overview

Improve existing service logs to require severity level set on all service logs and require an action_required boolean for each service log sent.

User Story #1 As a cluster owner/administrator, I need to receive a notification in the form of a service/history log for events that Red Hat SRE identifies or manages and for those that I need to take action on.

• [P0] The Service Log must identify the Severity: Info, Warning, Major, and Critical. 
• [P0] The Service Log must identify if action is required or not by the recipient in the subject line.
• [P0] The Service Log includes links to Documentation, Knowledge-base articles and Red Hat support site for opening a case.
• [P0] The Service Log is uniform across ROSA, OSD, ARO
• Service Log must have an action_required boolean

Acceptance Criteria
The list of requirements to be met to consider this Epic feature-complete

**

Done Criteria

• All Acceptance Criteria are met
• All existing/affected SOPs have been updated.
• New SOPs have been written.
• Internal training has been developed and delivered.
• The feature has full, automated test suites passing in all pipelines.
• If the feature requires QE involvement, QE has signed off.
• The feature exposes metrics necessary to monitor.
• The feature has had a security review / Contract impact assessment.
• Service documentation is fully updated and complete.
• Product Manager signed off.

References
Links to Gdocs, GitHub, and any other relevant information about this epic.