[#8827] Change Style/FormatStringToken style to template internally

[pirj]

Related: #8827

Extracted from #10723

---

Before submitting the PR make sure the following are checked:

• The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
• Wrote good commit messages.
• [-] Commit message starts with [Fix #issue-number] (if the related issue exists).
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• [-] Added tests.
• Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
• [-] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

[koic]

I'm going close this PR. Because the default change has not yet been finalized and different from the default doesn't look better.

[pirj]

the default change has not yet been finalized

@koic May I kindly ask you to elaborate on "finalized"?

As previously discussed:

I don't mind changing this for RuboCop itself (unless someone from https://github.com/orgs/rubocop/teams/rubocop-core objects)

And there were no objections to changing it for RuboCop itself.

I apologize for the possible confusion, I've mistakenly put the ticket as #8227, while it should have been #8827.

doesn't look better

When it comes to a point where subjective opinion, I we refer to the style guide.
The style guide recommends %<...> over %{...}, but this small research shows that the real-world usage is different.

The style guide's promise is:

A style guide that reflects real-world usage gets used, while a style guide that holds to an ideal that has been rejected by the people it is supposed to help risks not getting used at all - no matter how good it is.

Basing on this, I intend to propose a change to the Style Guide, and get back to this PR after. All for consistency across various Ruby codebases.

[pirj]

@koic ping