CrazyPhone

Fix photo item hotbar crash and 1.21.1-only recipe/port issues, bump version to 1.5.0-beta.2

• CrazyPhonePhotoItemRenderer: fetching both the front (FRAME_TEXTURE) and back/edge (BACKING_TEXTURE) VertexConsumers up front, before writing to either, crashed with "IllegalStateException: Not building!" the moment the photo item rendered in a hotbar slot - confirmed live on 1.21.1, and the same shared code affects every version including 26.1. The GUI/hotbar item-icon MultiBufferSource ends whichever buffer was last active as soon as getBuffer() is called for a different RenderType, even before anything is written to the new one, unlike the world's own buffer source which tolerates fetching several buffers ahead of time. Both renderFramedCard and renderHandFramedCard now fetch each buffer immediately before writing into it instead of caching both upfront.

• build.gradle.kts: the photo item's dye-crafting recipe uses "minecraft:crafting_dye", a recipe type that doesn't exist before 26.x - loading it on 1.21.1 failed the whole RecipeManager reload with "Unknown registry key ... minecraft:crafting_dye" (confirmed live). Dyeing still works fine there via the item's own "dyeable" tag and vanilla's built-in ArmorDyeRecipe, so the recipe JSON is now deleted from the build output on every version before 26.x, matching this task's own existing precedent for duplicate_photo.json.

• scripts/dev-launch.ps1: 1.21.1's assigned dev-server port (25568) didn't match build.gradle.kts' own "--quickPlayMultiplayer localhost:25565", which is hardcoded identically across every NeoForge node's client run config, not actually per-version - the 1.21.1 client's auto-connect failed with Connection refused as a result. Reassigned to 25565 to match, same as 26.1 already was - the two can no longer run their own dedicated servers at the same time, acceptable since neither is tested that way currently.