feat: ioc batch-search --info=locations + --limit

[maximelb]

Summary

CLI/SDK support for the new info and limit params on POST /insight/{oid}/objects (lc_api-go feat/batch-ioc-locations-info-param), which routes to insight-go's get_obj_batch_locations RPC (insight-go ac80936 / #280).

• Insight.batch_search SDK gains info (`summary` | `locations`) and limit kwargs.
• limacharlie ioc batch-search gains --info and --limit flags.
• Default behavior unchanged (`info=summary`, no limit) — existing callers keep getting the four-bucket prevalence response.
• The whole batch still consumes a single ioc-search rate-limit charge regardless of --info. That gateway-level protection is what makes the batch endpoint preferable to fanning out per-IOC search calls.

Test plan

• tests/unit/test_sdk_insight.py covers default info=summary, info=locations, limit included/excluded.
• Full unit suite still passes (957 passed; 1 pre-existing TOON optional-dep failure on cli-v2 unrelated to this PR).
• Manual: run `limacharlie ioc batch-search --input-file iocs.json --info locations --limit 50` against an org where insight-go has the new RPC deployed.

Depends on

• lc_api-go feat/batch-ioc-locations-info-param branch (32d7bbf, 40c3ce6)
• insight-go Migrate billing endpoints from billing-service to lc_api-go #280 (merged, in v<latest tag>)

🤖 Generated with Claude Code