Further enhance 0.5 migration scalafix

[bpholt]

I think this covers the migration cases I was looking for, with the exception that I haven't been able to figure out how to globally replace tagChunkSize with ChunkSize and also have it work inline in a encrypt method call without publishing two separate rules.

Unless anyone has any great ideas, on Monday I'll probably start working on a second rule and documentation stating "run the tagChunkSize → ChunkSize rule first" and then the more universal rule second.

[bpholt]

@CJSmith-0141 Do you have any suggestions here?

[CJSmith-0141]

The advice from this post by @/bjaglin on the scalameta discord is:

You should always aim at patching the smallest tree possible

So I think that you're on the right track with your commented out code here

Maybe a strategy like you did with migrateEncrypt ? Write a private function that does the tagChunkSize migration and invoke it in two places

• at the top level but with a predicate to ensure that match isn't a child of any encrypt using Tree.parent
• another time in migrateEncrypt

[CJSmith-0141]

I took a shot at it in #238 targeting this branch.

[bpholt]

@CJSmith-0141 I incorporated your suggestion from #238 and took it a step further. I think this is pretty close to being ready to merge and release; what do you think?

[CJSmith-0141]

LGTM, thank you for putting time into this @bpholt