Enable global playerbot opportunity planning

[adrunkhuman]

Summary

• Remove fixed temple and current-position cutoffs from hunt, service, trainer, equipment, reward, and depot opportunity discovery.
• Keep global hunt selection bounded with optimistic projected-XP ordering and stop after the best proven reachable candidate cannot be beaten.
• Register static StdModule.travel offers and use normal NPC dialogue, payment, and destination verification for bounded multi-hop boat and carpet routes.
• Restore Bot One to a pristine level-8 Knight baseline so progression decisions start from ordinary equipment, skills, and funds.

Verification

• pwsh -File scripts/bootstrap-client.ps1 - pinned client runtime and assets were ready.
• docker compose -f server/compose.yaml config --quiet - configuration is valid.
• docker compose -f server/compose.yaml up --build --detach - release image built and the fresh disposable stack started.
• Fresh smoke - MariaDB was healthy, setup exited 0, exactly one valid Bot One registration existed, ports 7171 and 7172 accepted connections, and lifecycle reported 181 travel offers with 26 opaque offers.
• Hunt smoke - scored 5,635 regions, found 500 suitable, validated one 30,240-node route, deferred 499 lower-bound routes, and selected the Thais sewer rats. The server used about 2.08 GiB, returned to about 2.3% CPU, and had no OOM, restart, terminal event, or Lua error.

Limits

NPC shop, banker, Oracle, and trainer coverage still depends on incomplete playerbot_service metadata. Native capability discovery is tracked in #33. The final smoke selected a local hunt, so carpet and multi-hop travel were not exercised end to end after the final planner changes. New unit coverage and the full progression gameplay suite are deferred.

Advances #148.