Fixes issue where safe navigation is lost when it exists in the check. For example, "check if the variable is not nil and the method call foo on that object doesn't return nil, if so, call bar on the result, else nil":

variable&.foo ? variable.foo.bar : nil # bad

This fixes the autocorrect from the incorrect behavior that omits the original safe navigation, to the correct behavior that preserves the existing safe navigation.

variable.foo&.bar # incorrect
variable&.foo&.bar # fixed

Fixes:

- foo&.bar && foo.bar.baz
+ foo&.bar&.baz

- if foo&.bar; foo.bar.baz; end
+ foo&.bar&.baz

- foo&.bar ? foo.bar.baz : nil
+ foo&.bar&.baz

This relates to a comment I placed in #14420. Fixing the issue with this PR rather than opening a new issue.

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.