Added conditions to RegistriesDatapackGenerator

[Rover656]

Added the ability to pass a list of conditions into RegistriesDatapackGenerator (+ DatapackBuiltinEntriesProvider by extension) to allow generating conditional datapack registry objects.

This was the best was I could think of implementing this functionality whilst having the smallest impact on the patches, but please let me know if I've missed anything!

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

[Technici4n]

I don't think that this works too well. The conditions should ideally be per-entry.

[Rover656]

I don't think that this works too well. The conditions should ideally be per-entry.

Without changing too much of the machinery, the best idea I could think of for this is accepting a Map of ResourceKeys/ResourceLocations containing a list of the conditions for those records? Unsure of what else to do given how this generator works

[Technici4n]

Yeah, I suppose that having a "builder" for the ResourceKey -> ICondition[] mapping is not too bad.

[Rover656]

I've gone ahead and switched this to use a map between ResourceKey and a list of conditions, instead of applying all conditions to the whole provider.

Constructors are provided both to accept the map directly, or with a builder (I can make this strongly typed instead of a Consumer<BiConsumer<...>> if preferred).

[Technici4n]

Could you write some tests for this? No need for crazy checks of course, just a bit of datagen code. I think it would be good to get a feel for the API on the datagen side.
(Note: I haven't looked at it yet).

[Rover656]

Could you write some tests for this? No need for crazy checks of course, just a bit of datagen code. I think it would be good to get a feel for the API on the datagen side. (Note: I haven't looked at it yet).

I'll look at doing that just now :)

[Rover656]

I've added some tests now that should demonstrate the behaviour :)