feat(go): add stream/topic purge API with BDD tests and fix server purge bug

[chengxilo]

Which issue does this PR address?

Relates to #2148

Rationale

Go SDK doesn't have the purge topic/ purge stream API, so this PR implement them. To test it, I added an new BDD test scenario, and implemented both Go and Rust BDD tests.

What changed?

The Go SDK was missing PurgeStream and PurgeTopic methods. Added them along with a shared BDD scenario (stream_topic_purge.feature) and implementations in both Go and Rust.

While testing, discovered that purge_all_segments only cleared on-disk segments but left stale messages in the journal and in-flight tiers. Polling after purge would return messages that should have been deleted. Fixed by calling journal.reset() and clear_in_flight() during partition re-initialization. I am not famliar with Rust server code so during the code review this part worth more attention

Local Execution

• Passed
• Pre-commit hooks ran

AI Usage

1. DeepSeek pro v4, Claude Opus 4.6
2. DeepSeek pro v4 for BDD test implementation, Claude Opus 4.6 for server bug fixing.
3. I reviewed them with my best effert, the bdd scripts are executed and actually works, and they found that there is a bug in the server so I believe they works.
4. I hope so.

[github-actions]

Thanks for the PR. It is labeled S-waiting-on-review and queued for review.

Slash commands (own line, regular comment) move it around the queue:

• /ready - back to S-waiting-on-review after addressing feedback
• /author - flip to S-waiting-on-author while you finish changes
• /request-review @user-or-team - request a reviewer

See CONTRIBUTING.md for details.

[codecov]

Codecov Report

❌ Patch coverage is 30.00000% with 14 lines in your changes missing coverage. Please review.
✅ Project coverage is 41.70%. Comparing base (b7c87d8) to head (9b5e79c).
⚠️ Report is 7 commits behind head on master.

Files with missing lines	Patch %	Lines
foreign/go/internal/command/stream.go	0.00%	4 Missing ⚠️
foreign/go/internal/command/topic.go	0.00%	4 Missing ⚠️
foreign/go/client/tcp/tcp_stream_management.go	0.00%	3 Missing ⚠️
foreign/go/client/tcp/tcp_topic_management.go	0.00%	3 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (50.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@              Coverage Diff              @@
##             master    #3608       +/-   ##
=============================================
- Coverage     73.61%   41.70%   -31.92%     
  Complexity      937      937               
=============================================
  Files          1297     1294        -3     
  Lines        143770   125001    -18769     
  Branches     119328   100620    -18708     
=============================================
- Hits         105842    52130    -53712     
- Misses        34562    70050    +35488     
+ Partials       3366     2821      -545     

Components	Coverage Δ
Rust Core	33.90% <100.00%> (-39.94%)	⬇️
Java SDK	62.44% <ø> (ø)
C# SDK	71.04% <ø> (-1.14%)	⬇️
Python SDK	92.17% <ø> (ø)
PHP SDK	84.29% <ø> (ø)
Node SDK	91.22% <ø> (-0.13%)	⬇️
Go SDK	42.59% <0.00%> (-0.13%)	⬇️

Files with missing lines	Coverage Δ
core/server/src/shard/system/segments.rs	89.43% <100.00%> (-0.49%)	⬇️
core/server/src/streaming/partitions/journal.rs	86.04% <100.00%> (+0.68%)	⬆️
foreign/go/client/tcp/tcp_stream_management.go	76.31% <0.00%> (-6.55%)	⬇️
foreign/go/client/tcp/tcp_topic_management.go	76.78% <0.00%> (-4.35%)	⬇️
foreign/go/internal/command/stream.go	83.78% <0.00%> (-10.16%)	⬇️
foreign/go/internal/command/topic.go	87.17% <0.00%> (-4.72%)	⬇️

... and 413 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hubcio]

@chengxilo i'll check this during the weekend. could you please rebase?

[numinnex]

I've checked whether there is potential concurrency issue due to interleaving of flush + purge commands as this is what I've reckon from the changes could potentially be an issue and did not find any problems with that. Let's wait for @hubcio review and we can merge it.

[chengxilo]

/ready

[chengxilo]

nothing has been changed, just because I rebased onto master locally so it was forced pushed() I shouldn't do that tho.