BlockGrowEvent is inconsistent for different type of blocks

Expected behavior

The block age must not get updated and must stay the same, same as before the grow.

Observed/Actual behavior

Cactus age still gets updated even after cancelling grow event.
Cactus is at age 0 -> BlockGrowEvent triggered -> Cactus is at age 1 -> Cancelling the grow event -> Cactus is still at age 1

Steps/models to reproduce

Make a cactus farm, size don't really matter.
Create a command that sends targeted block's block data.
Listen to BlockGrowEvent, maybe filter it to just cactuses.
Cancel the event.
Set the random tick speed gamerule high to test faster.
Use the command to see cactuses' datas. They'll have 15 age with just root block.

Plugin and Datapack List

[21:14:00 INFO]: ℹ Server Plugins (17):
[21:14:00 INFO]: Paper Plugins (3):
[21:14:00 INFO]: - FancyNpcs, RoseStacker, SkBee
[21:14:00 INFO]: Bukkit Plugins (14):
[21:14:00 INFO]: - Essentials, FastAsyncWorldEdit, Lands, LuckPerms, NBTAPI, packetevents, PlaceholderAPI, ProtocolLib, Skript, skript-reflect
[21:14:00 INFO]: uxmFarmer (my plugin), Vault, ViaBackwards, ViaVersion

Paper version

[21:13:53 INFO]: This server is running Paper version 1.21.10-129-ver/1.21.10@3e25649 (2025-12-19T23:34:30Z) (Implementing API version 1.21.10-R0.1-SNAPSHOT)
You are running the latest version

Other

I'm not sure if this is intented or not, I'm not saying it must be fixed right now but it really is weird and shouldn't happen. A person from Paper discord said the age data changes before BlockGrowEvent so its not really that event's fault, then there should be another event for this.
Please atleast discuss this. Also, not yet tried with other blocks like sugar cane and bamboo. Will try.
Also, also, happy new year!

Start by reproducing the cactus farm case with BlockGrowEvent, a cancelled listener, and the block-data command described in the issue. Compare the cactus age before the event, after cancellation, and after the random tick; done means establishing whether cancellation should preserve the age and identifying the appropriate event or API behavior for consistent block handling.