Promote blameless culture by using "annotate" instead

What does this MR do?

It helps promote blameless culture in software development teams.

The verb "Blame" in UI is replaced by "Annotate".

Are there points in the code the reviewer needs to double check?

I have made the easiest part — UI texts. Please let me know if I should proceed and change "blame" to "annotate" in other parts of the application:

• URI paths
• Class names
• everywhere else

Why was this MR needed?

The verb "blame" encourages developers to, well, blame their colleagues for mistakes. This is easy. But this is unhealthy and useless. We should strive to promote the culture of understanding and teamwork instead.

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

None. I have started with this PR right away.