Refactor replaceAllOccurences & add progress bar when applying actions

[friendlyhj]

I think this PR can slightly increase efficiency of this method.

In my test in an instance with GTCE, it reduces the time taken from 28 seconds to 11 seconds

[friendlyhj]

@jaredlll08 what's your thought?

[jaredlll08]

I like the progress bar stuff, I think that is really cool.

I'm not sure about the replacealloccurances though, the whole method has just been trouble and I'm scared that if we change it now, it may cause even more trouble.

How certain are you that it works and all is fine with it?

[friendlyhj]

It works well. Almost all recipes are corrently modified.

But in some recipes, there is an issue. If a recipe can use ingredient A or B (like IngredientOr ?), now I want to replace A with C. In previous implementation, the ingredient will be replaced to C. But In my implementation, it won't be replaced. The previous one maybe over-replace. But the my one cannot replace under certain condition. I don't know how to deal with it well. So I plan to add a function to let users determine when the ingredient should be replaced. (add a new method, the previous method will use previous matching way)

Now A or B will be replaced to C or B. It works perfectly now.

[friendlyhj]

@jaredlll08 ready for review

[jaredlll08]

Going forward with PRs, maybe mark them as a draft, and when you're ready for review just mark it as ready, just makes it easier to manage things.

I also want @kindlich's thoughts on it, but besides that it mostly looks good

[jaredlll08]

Looks good

[friendlyhj]

@jaredlll08 @kindlich when the PR is merged? I'm developing a modpack that needs the function.

[kindlich]

Looks good to me.
I added a few Codestyle suggestions to make SubActionReplaceAllOccurrences#apply easier to read ^^

Also, as a side note:
This implementation creates a different recipe name if a recipe is affected by multiple replaceAllOccurences calls. Prior implementation would append remodified, reremodified etc., This implementation will only append modifed.
That is fine by me, I just wanted to point it out.

Also, the previous implementation used IIngredient#contains(IIngredient) to match, whereas you do it manually and allow partial replacements. This can lead to different results if I'm not mistaken.
That is fine by me, I just wanted to point it out.

[friendlyhj]

SubActions only modify the recipe pattern, the ingredient array. After all sub actions are applied, if the ingredient array is modified (ActionReplaceAllOccurence.INSTANCE.recipeModified == true), the recipe will be modified. so, the recipe is modified only once. There is no reason for a reremodified recipe.
About these code style suggestion, I will change them tomorrow later.