Add config and registry to processed source if the methods exist

[renatolond]

Fixes issue with rubocop > 1.38.x

It seems that rubocop/rubocop#10987 introduced registry and config to new versions of rubocop which were not there before.
Without those, rubocop still works, but it raises a lot of errors for some files.

I added the registry and source like in the rubocop code if the ProcessedSource responds to it, so I'm hoping it won't break compatibility with older rubocop versions.

This fixes #76

[ashkulz]

@renatolond can you specifically add 1.38.0 to this line so that we check this? You'll probably need to add to the excludes as well for Ruby 2.3 and 2.4.

I'm also wondering why I don't get an option to trigger the CI run on this PR 🤔

[renatolond]

@renatolond can you specifically add 1.38.0 to this line so that we check this? You'll probably need to add to the excludes as well for Ruby 2.3 and 2.4.

I'm also wondering why I don't get an option to trigger the CI run on this PR thinking

Sure, done!

It's weird about the CI, I already saw the option of "allow run" for new contributors on some of my projects, but not showing at all is odd 🤔

[ashkulz]

@renatolond can you do a rebase or something? I triggered a run manually, apparently scheduled actions got suspended on this repo, which were supposed to inform me about regressions -- another fun thing to research 🙈

[renatolond]

@ashkulz Sure, done! :)

[ashkulz]

Looks like there's a typo, @renatolond 🙂

[ashkulz]

Thanks for the contribution, @renatolond! I'll push up a release by EOD.

[renatolond]

Thanks for the contribution, @renatolond! I'll push up a release by EOD.

Thank you, @ashkulz 🎉

[ashkulz]

Released to RubyGems: https://rubygems.org/gems/pronto-rubocop/versions/0.11.3