Fix cancelled rooted dirt drops being duped

[HaHaWTH]

This PR fixes #13536, cancelled rooted dirt drops being duped

Analysis

protected static final Map<Block, Pair<Predicate<UseOnContext>, Consumer<UseOnContext>>> TILLABLES = Maps.newHashMap(
        ImmutableMap.of(
            Blocks.GRASS_BLOCK,
            Pair.of(HoeItem::onlyIfAirAbove, changeIntoState(Blocks.FARMLAND.defaultBlockState())),
            Blocks.DIRT_PATH,
            Pair.of(HoeItem::onlyIfAirAbove, changeIntoState(Blocks.FARMLAND.defaultBlockState())),
            Blocks.DIRT,
            Pair.of(HoeItem::onlyIfAirAbove, changeIntoState(Blocks.FARMLAND.defaultBlockState())),
            Blocks.COARSE_DIRT,
            Pair.of(HoeItem::onlyIfAirAbove, changeIntoState(Blocks.DIRT.defaultBlockState())),
            Blocks.ROOTED_DIRT,
            Pair.of(useOnContext -> true, changeIntoStateAndDropItem(Blocks.DIRT.defaultBlockState(), Items.HANGING_ROOTS))
        )
    );

The rooted dirt item drop logic is being processed in HoeItem#useOn, the drop capturing isn't enabled in this path, causing hanging roots to still be dropped even BlockPlaceEvent is cancelled.
This bug has existed since 1.19, after Mojang added the rooted dirt.

[Astralchroma]

Paper devs gotta merge this quick before my Server's Rooted Dirt economy experiences hyperinflation!!1! Simply the best currency imaginable.

I know this will immediately get hidden as being spam or off-topic or whatever but I thought it was a funny joke.

[electronicboy]

This really falls into my qualms about how this logic works in general, it feels messy but it also smells like that is just how this stuff has to work for now

[lynxplay]

I am a bit confused on the path here.
Why double the variable when the serverLevel.captureDrops exists?

Are we trying to handle the case where this field is non null? In that case, we'd have to store current state and restore later, which we are not doing. If we aren't (which I don't think we need to? captureDrops is for the mineBlock bit, that shouldn't trigger useOn), we don't need such added changes that check for possibly null lists (e.g. if (capturedDrops != null) { below too)

[HaHaWTH]

Thanks for the suggestion, I was engaging in a bit of defensive programming there with the extra checks, but I see now it wasn't necessary given the context.