Add the HeatCondition API to allow the creation of alternate heating types under basins

[vercte]

This PR creates the HeatCondition interface, which defines how a basin should check if a heating requirement is satisfied.

It also provides methods for displaying the recipe in JEI: A method for rendering an IDrawable in the Category, a method for providing "hint items" (blaze burner, blaze cake), and a method to get the color that the Heat Condition's name will be displayed as.

This PR also creates the HEAT_CONDITION registry, which is used to register these HeatConditions and serialize them into recipes.

Basin Recipes have changed, with the heatRequirement field being now a namespaced value (create:heated, example:cooled) with create as the default (this is to maintain backwards compatiblity; don't want to break literally every datapack 😅)

An example usage of this is linked in this gist: https://gist.github.com/vercte/fe67c1bc6649c287f84905eb9cbfb2fb

[vercte]

This apparently makes Create require JEI. I'll have to fix that

[Syndaryl]

Could you consider also support for EMI? REI will probably also be necessary once Create 6 Fabric is ready. That should cover the current Big Three recipe viewers.

[IThundxr]

Could you consider also support for EMI? REI will probably also be necessary once Create 6 Fabric is ready. That should cover the current Big Three recipe viewers.

Create forge does not natively have support for EMI so only supporting a few things with EMI is not good choice

[github-actions]

@vercte, this pull request has merge conflicts with the target branch. Please merge the latest changes and leave a message here so we can continue with the process of reviewing and merging this pull request. Thanks!

[vercte]

merged with the current state of the Create repo