Stonecutting recipes don't use tags, making the maintenance of stonecutting recipes via game's code less efficient

Despite technically accepting tags, stonecutter recipes do not utilize them, resulting in a less efficient maintenance of crafting recipes. This means, for example, that instead of a stonecutting recipe for, let’s say, Deepslate Tiles, having a tag containing Cobbled Deepslate, Polished Deepslate and Deepslate Bricks, and this tag being used for a single stonecutting recipe for Deepslate Tiles, the game instead utilizes separate recipes: one for Cobbled Deepslate → Deepslate Tiles, one for Polished Deepslate → Deepslate Tiles, and another for Deepslate Bricks → Deepslate Tiles, even though these recipes could be merged into one by using a tag. This is just one example, as it also happens with several other recipes.

Steps to reproduce:

1. Go to the game’s files and look for data/minecraft/recipe

2. Search for any block stonecutting recipe with multiple possible materials as their recipe input (example: ‘deepslate tiles stonecutting’)

3. If the stonecutting recipe searched is for a full block, check the last files that appear in the row upon search. It’s necessary because the search bar prioritizes alphabetical order, meaning that non-full block recipes made from the full block in question appear first.

Expected results:
Stonecutting recipes for blocks with multiple possible materials as their input are contained within a single file, with the input being an item tag with the materials in question.

Actual results:
If the block in question can be made with multiple possible materials as their recipe input, separate files for each possible input are used instead, which compromises flexibility.

Notes:
This issue first appeared in 19w04a