Pillagers spawned during a raid have their `CanPickUpLoot` NBT tag set to false

Pillagers that spawn as part of a raid have their CanPickUpLoot tag set to 0b, regardless of the default value for pillagers (which is 1b in normal circumstances). This can be verified via /data get.

Note: This report focuses specifically on pillagers. Other raider types (vindicators, evokers, etc.) have a default CanPickUpLoot value of 0b. The anomaly here is that pillagers – which normally default to 1b – are being forcibly overwritten to 0b by raid initialization.

Note regarding MC-199256:
This forced 0b initialization appears to be the only known case where a pillager can exist with CanPickUpLoot:0b in a way that bypasses the permanent write‑lock described in MC-199256 (where summoned pillagers have an untoggleable CanPickUpLoot tag locked to 1b). Because raid‑spawned pillagers start at 0b, the 0→1 transition is still possible – but only once. After being manually changed to 1b, they become subject to the same permanent lock as all other pillagers.

Steps to reproduce:

1. Trigger a raid and allow pillagers to spawn.

2. Select a pillager that spawned as part of the raid.

3. /data get entity @n[type=minecraft:pillager] CanPickUpLoot
   → Returns 0b