Avoid changing the sigils of files not bumped

[Morriar]

Let's consider this RBI file:

# file1.rbi
# typed: true
class A
  def foo(a, b, c); end
end

We can create a conflict of signature when turning this file to true:

# file2.rb
# typed: false
class A
  def foo(a, b); end
end

When this happens an error will be reported for both file1.rbi and file2.rb which prompted spoom bump to revert the file to typed: false even if it was not bumped in the first place.

This PR fixes this behaviour by reverting only the sigil for files that were bumped.

Fixes #85.

[KaanOzkan]

Is it possible to not even make this suggestion in the first place?

[Morriar]

I honestly don't know how to do so.

One way would be to parse the error message for file2.rbi and see that the first help section points to file1.rb. But the help sections points to a bad method more often than the other way around.

Any idea?

[KaanOzkan]

Isn't it safe to assume if an already true file gave a redefined without matching argument count error it would have to be the file inside help section? We can also make sure that the file inside help section was bumped.

This solution does assume typecheck passes before running spoom.

[Morriar]

As per our conversation on Slack: let's merge as this and improve later 👍