git-rename-tag: add page

[CleanMachine1]

• The page (if new), does not already exist in the repo.
• The page is in the correct platform directory (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.
• The page description includes a link to documentation or a homepage (if applicable).

For #5137

See #5950 for what I based this on

[CleanMachine1]

If no commits/changes are made can this be rebased since it is only 1 commit?

[marchersimon]

Looks good. Why do you want it to be rebased? As far as I know it doesn't make any difference if there is only one commit.

[CleanMachine1]

Yes but this is acceptable to rebase

[bl-ue]

It's perfectly fine for it to be rebased; however, since it's not necessary and we normally squash I'd prefer to squash. The added benefit (which is my primary motive) is that squashing causes the PR number to be in the commit message, which is very helpful for navigating. Rebasing causes the commit to go directly to the main branch unmodified (except that the the merger is attributed as "committer").

@CleanMachine1 if you still want to, we can go ahead and rebase this PR but I don't want to make it a habit :)

[CleanMachine1]

Only because this is one commit.

I'll leave the PR in the title

[bl-ue]

No problem — it doesn't matter that much.