Improve codebase's message template

[Niloth-p]

Add backticks for branch names.
Motivation: Updating example screenshots in integration docs.

---

How did you test this PR?
I did not test the changes.

---

I added the automatic changes on linting and formatting (on editor save) as the first commit, so that the actual functional changes are identifiable clearly in a separate commit.

Would we prefer to:

• Do this sort of formatting updates to all the files together? In that case, should I remove the changes in the first commit, and just add backticks to the templates in the format() calls?
• Merge this and worry about the rest later?

Self-review checklist

• Self-reviewed the changes for clarity and maintainability
  (variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

• Explains differences from previous plans (e.g., issue description).
• Highlights technical choices and bugs encountered.
• Calls out remaining decisions and concerns.
• Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

• Each commit is a coherent idea.
• Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

• Visual appearance of the changes.
• Responsiveness and internationalization.
• Strings and tooltips.
• End-to-end functionality of buttons, interactions and flows.
• Corner cases, error conditions, and easily imagined bugs.