SK-3061: add path to Token; fix stale samples pom.xml version

[Devesh-Skyflow]

Summary

1. Token.getPath()

flowdb_dp_apis.proto's own literal example response for insert includes a "path" key on token entries for a structured column:

"address": [
  {"path": "street", "token": "AMmmtFZyRO", "tokenGroupName": "nondet_trans_reg"},
  {"path": "phone_numbers[0].type", "token": "1e4c7e6b-...", "tokenGroupName": "det_rtf"}
]

— present when tokenizing a nested field within a structured column's own value, absent for flat columns (e.g. "email", "age" in that same example never carry it). Token.toToken()/parseTokens() silently dropped this key entirely; nothing in the SDK exposed it.

• Added Token.getPath() (nullable) and a new 3-arg constructor Token(token, tokenGroupName, path). The existing 2-arg constructor delegates to it with path=null — purely additive, no existing signature changed.
• Token.parseTokens() now reads "path" from each raw entry when present.
• Token.toRawTokens() (getFields()'s deprecated rendering) only adds a "path" key when the Token actually has one, rather than unconditionally — so a path-less round trip stays exactly as lossless as it was before path existed. (Adding it unconditionally would have given testToRawTokens_isTheInverseOfParseTokensForMapShapedInput a spurious "path": null key it never had — caught this while writing the fix, before it became a real regression.)
• Updated Token's Javadoc and the README's Bulk Insert Token section.

Compatibility: purely additive — confirmed via japicmp: BUILD SUCCESS, zero incompatibilities, no baseline regen needed.

2. flowvault/samples/pom.xml's stale dependency version

Pinned skyflow-flowvault-java to 3.0.0-beta.13-dev.18f8f1ba — a private dev-build version string carried over by mistake from the unrelated flowvault-release/26.8.1 branch when b3cf7375 (SK-3002 release/26.8.1 #386) switched the sample's dependency from skyflow-java (v2) to skyflow-flowvault-java. Pinned to 1.0.1, the actual latest public GA release.

3. Revert: bulkInsert (sync) structural exception-handling fix from #412

#412's second commit moved processBulkInsertSync's call to insertBatchFutures inside its own try, fixing a raw-exception leak via a throwing RequestInterceptor. Further investigation showed the same gap (missing SkyflowException-passthrough / generic Exception catch) exists identically in bulkDetokenize/bulkDeleteTokens/bulkTokenize's own outer catch lists too — not just bulkInsert's — so a narrower, operation-specific structural fix isn't the right shape for this. Reverted here pending a uniform fix across all four sync methods (tracked separately, not yet decided).

Removed testBulkInsert_unexpectedExceptionWrappedAsSkyflowException, which tested the now-reverted behavior.

Testing

• mvn -pl common,flowvault -am test -Dtest='!TokenTests#testExpiredTokenForIsExpiredToken' -DfailIfNoTests=false → 708 tests, 0 failures.
• mvn -pl common,flowvault -am verify -Dgpg.skip=true (same exclusion) → BUILD SUCCESS.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (flowvault-release/26.8.13@894a042). Learn more about missing BASE report.

Additional details and impacted files

@@                     Coverage Diff                      @@
##             flowvault-release/26.8.13     #413   +/-   ##
============================================================
  Coverage                             ?   91.46%           
  Complexity                           ?      493           
============================================================
  Files                                ?      159           
  Lines                                ?     6478           
  Branches                             ?      865           
============================================================
  Hits                                 ?     5925           
  Misses                               ?      361           
  Partials                             ?      192           

Flag	Coverage Δ
common	88.39% <ø> (?)
flowvault	89.19% <100.00%> (?)
skyvault	94.72% <ø> (?)
unittests-flowvault	90.07% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Module: common	88.39% <0.00%> (?)
Module: skyvault	94.72% <0.00%> (?)
Module: flowvault	89.19% <0.00%> (?)
Service Account	86.69% <0.00%> (?)
Vault Data	92.01% <0.00%> (?)
Vault Tokens	99.03% <0.00%> (?)
Vault Connection	100.00% <0.00%> (?)
Vault Controller	85.21% <0.00%> (?)
Detect	100.00% <0.00%> (?)
Audit	100.00% <0.00%> (?)
BIN Lookup	100.00% <0.00%> (?)
Config	96.26% <0.00%> (?)
Utils	89.45% <0.00%> (?)
Errors	100.00% <0.00%> (?)
Enums	100.00% <0.00%> (?)
Logs	95.34% <0.00%> (?)

Files with missing lines	Coverage Δ
.../com/skyflow/vault/controller/VaultController.java	77.95% <100.00%> (ø)
...lt/src/main/java/com/skyflow/vault/data/Token.java	96.72% <100.00%> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 894a042...65179ed. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.