Molang tag check in digger component does not work for non-host players.

Verification Builds: 1.16.100.60

Regression Build: new feature

Summary: The following digger component will work as expected for the host of the world however when a non-host tries to use the tool they will only be able to break eden:blockade_thorns. This seems to mean that molang tag checks do not work for no-host players. Explicitly specifying the block like in the third section does work. (The absurdly large numbers are because some blocks are meant to be unbreakable unless the tool is used.)

"minecraft:digger": {
		"use_efficiency": true,
		"destroy_speeds": [
			{
				"block": {
					"tags": "query.any_tag('eden:growable_plant')"
				},
				"speed": 1000000
			},
			{
				"block": {
					"tags": "query.any_tag('eden:plant_scrap')"
				},
				"speed": 1000000
			},
			{
				"block": "eden:blockade_thorns",
				"speed": 4000
			}
		]
	}

Impact: This poses a significant trouble when wanting to have a tool be effective against a large number of block as we are attempting to do. Having to specify each block identifier is a slow and unsustainable workflow.

Repro steps:
1. Create a behavior pack with a custom tool with a digger component similar to the one shown above.
2. Create blocks that match the tag and identifier tests of the digger component
3. Have another player join and try to break the specified blocks with the tool.

Observed Results: The molang block tag checks do not allow non-host players to break blocks with the specified tags. The host player is unaffected by this issue.

Expected Results: This molang tag check should work for both host and non-host players.

Screenshots/Videos attached: No