Added performance guidelines for new MRs

What does this MR do?

This MR adds a set of guides that should be followed by merge request authors.

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

Spelling, grammar, etc

Why was this MR needed?

There is no set of guidelines one should follow when submitting merge requests. This leads to developers at times disregarding performance. This in turn results in performance specialists having to clean up the mess, or production engineers being woken up in the middle of the night because the database is on fire.

Does this MR meet the acceptance criteria?

• Documentation created/updated
• Tests
  • All builds are passing
• Conform by the style guides
• Branch has no merge conflicts with master (if you do - rebase it please)
• Squashed related commits together

cc @DouweM @rspeicher @pcarranza @dzaporozhets