Port to 26.1-pre-1

[Ampflower]

This also has a side-commit of fixing the Neoforged Maven URI.

Various acknowledgements of subpars:

• render* methods that overrode Vanilla have been renamed to extract*RenderState
  • This did not cover the whole API surface, as we'd like further input whether all remaining render* functions should follow the same convention of extract*RenderState or extractGui in the case of rendering a screen.
• The NeoForge GUI render event hook has currently been commented out as it's unknown whether NeoForge will retain the same API name or use a new one. Given the hook is still named from MCP, it's quite likely it'll still be the same and the comment can be merely removed. But as there's no production NeoForge yet, it cannot be tested.
• GuiGraphicsAccessor has not been renamed yet.
• There are other renames in Vanilla code that has not been yet reflected in SpruceUI. Should those also be renamed to match the Vanilla counterpart?
• Yumi has been left on snapshot 6; have yet run into a code path that causes a crash, but it doesn't mean it does not contain a codepath that hasn't been tested that crashes.

[LambdAurora]

Thanks a lot!

I definitely would:

• do more renames to the extract*RenderState scheme, it's more accurate and can't live in the past all the time;
• rename the GuiGraphics mixin to make it fit the new name;
• not rename SpruceGuiGraphics because it's already quite long 😅;
• rename methods in SpruceGuiGraphics so the pass-through methods still match GuiGraphicsExtractor so we avoid potentially confusion.

[LambdAurora]

Currently the NeoForge signature is still the same.

https://github.com/neoforged/NeoForge/blob/7e61b8a35f1c0087ee07ca1d09db0c8452a6521a/patches/net/minecraft/client/renderer/GameRenderer.java.patch#L50

Though, it may still change which puts us in a delicate spot for now.
Arguably, it'd be much nicer if they used mixins for this. >:(

[Ampflower]

I'll leave it as-is in the meantime. Tho, saying that, the vanilla call is missing in NeoForge, so; it'll, break either way of: it's left commented out, always causing a mixin error on startup, or it's active but they changed the name mid-way through, causing a mixin error on startup then.