feat: allow remote deployment of place_monster items, throwable manhacks

[chaosvolt]

Purpose of change

This is a thing that @Lorith had requested support for way back in 2018 (CleverRaven/Cataclysm-DDA#26418). The issue got closed for "DDA doesn't care about fixing janky behavior if only mods will benefit from it" reasons, but it's not that hard to envision a perfectly vanilla use case for this.

Describe the solution

C++ changes:

1. In iuse_actor.cpp, set place_monster_iuse::use so that place_monster items with place_randomly set to true will use the item's position instead of the players. This allows for monster-spawning items that activate when thrown, instant monster spawns using drop_action, etc without them instead automatically spawning next to the player. Failure to place also unsets the item as active to prevent !!FUN!! involving explosively infinite spawns of a manhack that tried and failed to spawn after being thrown (as ACT_ON_RANGED_HIT sets the item in question to count as active). Lastly, thanks to Shard/Lorith deployment by being thrown doesn't consume additional moves.

JSON changes:

1. Gave all inactive manhacks/bombhacks the ACT_ON_RANGED_HIT flags, allowing you to yeet them for remote deployment (useful for tossing from behind cover as a distraction, for example).
2. Audited the weights of all inactive hacks to be not much higher than the weight of all components. This increases throwing range a bit for most, for example a strength-8 character can now toss a standard manhack 3 tiles instead of 2.
3. Additionally added flags to eyebots and set their action to place randomly, and reduced their size a bit. Weight now includes the weight of original components plus a security camera and 1 sheet metal, while volume reduced down to 20 liters (slightly above the audited volume of a mininuke hack). It's still a lot more than most characters could reasonably throw, but does put it more in reach for mutant characters.
4. Accordingly, updated recipe and uncraft for eyebots to use/yield a security camera and 24 small metal sheets.
5. Updated weights and volumes for broken hacks/eyebots accordingly.

Describe alternatives you've considered

Not adding throwable manhacks and only adding the code support.

Testing

1. Checked affected JSON files for syntax and lint errors.
2. Compiled and load-tested.
3. Chucked a manhack 3 tiles away from me, it correctly deploys on the tile it was thrown to and not next to me (though it's still close enough that it immediately moved over to me due to spawning hostile).
4. Chucked it even farther away with more strength to confirm it still spawns away from me and not next to me.
5. Chucked a manhack at a debug monster, it spawns next to the monster as expected.
6. Chucked it while surrounded by debug monsters, confirmed that it prints the relevant message and drops the manhack as an item on the tile next to me.
7. Debug-killed the debug monsters, confirmed no infinite death swarm of manhacks appears like what happened in my very first test of this.
8. Checked affected C++ file for syntax and lint errors.

Additional context

I'd like to also allow it to support having ALLOWS_REMOTE_USE too, but right now that causes an error if activated from within inventory. If we can figure out how to fix that then we can allow for not requiring you to pick up the heavier bots when deploying them.

Checklist

[chaosvolt]

Hmm. Getting a problem when activating from within inventory:

 DEBUG    : Tried to find where of an item without a location

 FUNCTION : where
 FILE     : C:\Users\Vincent\Documents\GitHub\Cataclysm-BN\src\item.cpp
 LINE     : 10273
 VERSION  : BN d9ebeade9d4d-dirty

[chaosvolt]

Found it, cause was from giving the manhacks the ALLOWS_REMOTE_USE flag.

[scarf005]

commenting code good