Issue title: Style/FormatStringToken with --disable-uncorrectable can't handle multiline strings
 Issue body: ## Expected behavior

When rubocop disable statement via `--auto-correct --disable-uncorrectable` is added, it should handle multiline strings.

## Actual behavior

It does not handle multiline strings and adds the `# rubocop:disable Style/FormatStringToken` in a place, where it breaks the code.

## Steps to reproduce the problem

For this code in `foo.rb`
```
 puts format('loaded %d references in ' \
       '%.1f ms (%.1fms per ref)', 10, 100, 10)
```
Then execute the cop
```
rubocop foo.rb --auto-correct --disable-uncorrectable --only 'Style/FormatStringToken'
```
Result
```
 puts format('loaded %d references in ' \ # rubocop:disable Style/FormatStringToken
       '%.1f ms (%.1fms per ref)', 10, 100, 10)
```
This leads to a syntax error
```
$ ruby foo.rb 
foo.rb:1: syntax error, unexpected escaped space, expecting ')'
...t('loaded %d references in ' \ # rubocop:disable Style/Forma...
foo.rb:2: syntax error, unexpected ',', expecting end-of-input
...    '%.1f ms (%.1fms per ref)', 10, 100, 10)
```


## RuboCop version
```
0.73.0 (using Parser 116.69.203.115, running on ruby 2.6.2 x86_64-darwin18)
```

 Comments: 
 Comment 0: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!

 Comment 1: This is still an issue.
 Comment 2: The problem in the description can not be reproduced in newer versions of RuboCop. After the PR #7409 the `Style/FormatStringToken` cop no longer detects offenses in strings that are split into multiple lines with backslashes.

Is there another cop where the same problem can be reproduced, or should we fix `Style/FormatStringToken`? Cc: @buehmann 
 Comment 3: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!

 Comment 4: This issues been automatically closed due to lack of activity. Feel free to re-open it if you ever come back to it.

{'source': 'GithubIssues', 'repo_name_with_owner': 'rubocop-hq/rubocop', 'issue_id': 469290685, 'repo_stars': 2682.0}