Please address the comments from this code review:

## Overall Comments
- The new shared `resource.FindResource` logic is noticeably less flexible than the previous `MapTracker`/`ItemTransfer` implementations (e.g. no stripping of leading `resource/`, no parent-of-resource-path search), which may break existing deployment layouts; consider adding equivalent fallback patterns so behavior remains backward compatible.
- The removal of `MAAEND_ITEMTRANSFER_DATA_DIR` support changes how `item_order.json` can be overridden/located; if this env-based override is still needed in some environments, consider reintroducing it inside the shared `resource` package rather than dropping it entirely.

## Individual Comments

### Comment 1
<location path="agent/go-service/pkg/resource/resource_sink.go" line_range="29-37" />
<code_context>
-type resourcePathSink struct{}
-
-// OnResourceLoading captures the resource path when a resource is loaded.
-func (c *resourcePathSink) OnResourceLoading(resource *maa.Resource, status maa.EventStatus, detail maa.ResourceLoadingDetail) {
-	if status != maa.EventStatusSucceeded || detail.Path == "" {
-		return
</code_context>
<issue_to_address>
**issue (bug_risk):** The stored resourcePath is a file path but later treated as a base directory, which can produce invalid joined paths.

`OnResourceLoading` stores `detail.Path` (or its absolute form) directly in `resourcePath`, and `getResourceBase` returns it. `FindResource` then calls `filepath.Join(base, rel)`. When `detail.Path` is a file path (the usual case), `base` is not a directory, so the join yields invalid paths like `/path/to/some.png/data/ItemTransfer/item_order.json`. The old `FindResource` logic handled this by using `filepath.Dir(base)`; the new helper does not. Either store `filepath.Dir(absPath)` as the base, or have `getResourceBase` wrap the stored path with `filepath.Dir` before joining.
</issue_to_address>

### Comment 2
<location path="agent/go-service/itemtransfer/types.go" line_range="57" />
<code_context>
-			return
-		}
-		b, err := os.ReadFile(filepath.Join(dir, "item_order.json"))
+		b, err := resource.ReadResource("data/ItemTransfer/item_order.json")
 		if err != nil {
 			cachedDataErr = err
</code_context>
<issue_to_address>
**question (bug_risk):** Removing the custom directory search (incl. env override) may break deployments that rely on MAAEND_ITEMTRANSFER_DATA_DIR or deeper search paths.

The previous `loadItemOrderData` respected `MAAEND_ITEMTRANSFER_DATA_DIR`, walked multiple parent directories, and fell back to paths like `assets/data/ItemTransfer`. Switching to `resource.ReadResource("data/ItemTransfer/item_order.json")` drops the env override and narrows the search to a few fixed locations. If existing deployments depend on that configurability, this is a breaking change. Consider wiring the env-based base directory (or equivalent) into `getStandardResourceBase` or this call so those setups continue to work.
</issue_to_address>