sorbet_removal_commit doesn't take into account a re-addition

[KaanOzkan]

Spoom incorrectly displays that a project has removed sorbet

The logic could check if sorbet/config has been introduced again since it's been removed (intro date > removal date) and not populate removal_commit.

[Morriar]

I'm not sure I agree with this issue.

The library does its job and correctly tells you when the sorbet/config file was removed for the last time from Git index.

I think it's up to the library client to do what makes sense with this information and compare both the last intro date and last removal date.