Standardize the column names on Events tabs

[TheGostKasper]

Closes #3376
Currently some of our Events tabs use wording that is different from other Events tabs. But there's just one schema for Event objects. To prevent user confusion, let's standardize so that every Events tab includes these four column names:

• Reason
• Message
• From
• Last Updated

This involves the views:

• GitOpsSets (Reason, Message, From, Last Updated) -- leave as-is
• Delivery (Reason, Message, From, Last Updated) -- leave as-is
• Secrets (Reason, Message, Age--remove this one) -- adjust
• Terraform (Reason, Message, From, Last Updated) -- leave as-is
• Applications (Reason, Message, Component, Timestamp) -- adjust
• Sources (Reason, Message, Component, Timestamp) -- adjust
• We also wish to apply a tooltip to the "Reason" column name to make its meaning clearer. This tooltip should say: " "Reason" refers to what triggered the event. It can be different according to each component."

Acceptance Criteria:

• All of the listed views above feature the same column names on their Events tabs.
• All of the affected views feature the "Reason" tooltip.
• A tiny "information" icon (thinking an i-in-a-circle) appears next to "Reason."
• A tiny information icon appears next to From.
• The user can trigger the tooltips by hovering over the "information" icon.
• The tooltips appear within one second.

redirect3-2023-10-02_13.45.47.mp4

[opudrovs]

Will be reviewed after the OSS PR.

[opudrovs]

Sorry, commented here instead of the OSS PR, will get to this one now.

[opudrovs]

I think the comma before "and" is not needed here because "and" connect two verbs. But English punctuation is not my strong suit.

[TheGostKasper]

@opudrovs #3376 (comment)

[opudrovs]

Tested it locally, LGTM! 🎉