Fix issues found by long-running and stress tests

[hanahmily]

Currently, I am conducting several long-running stress tests in preparation for release 0.5.0. These tests have led to the discovery of several bug fixes and improvements.

Bugs:

1. The buffer is closed unexpectedly, which results in write failure.
2. Flushing with an empty time range causes the data not to be written on the disk.

Improvements:

1. Introduce an on-disk query suite case to verify the scenario when all data is flushed on the disk.
2. Introduce CPU and Heap profile when running the stress test.
3. Print the primary test result after executing the stress test successfully.

[codecov-commenter]

Codecov Report

Merging #342 (1db4f76) into main (2cf42aa) will decrease coverage by 0.56%.
Report is 2 commits behind head on main.
The diff coverage is 47.08%.

@@            Coverage Diff             @@
##             main     #342      +/-   ##
==========================================
- Coverage   39.87%   39.32%   -0.56%     
==========================================
  Files         111      112       +1     
  Lines       11938    12329     +391     
==========================================
+ Hits         4760     4848      +88     
- Misses       6709     7003     +294     
- Partials      469      478       +9     

Files	Coverage Δ
banyand/measure/service.go	89.47% <100.00%> (+0.18%)	⬆️
banyand/metadata/client.go	44.51% <100.00%> (+1.09%)	⬆️
banyand/metadata/schema/schema.go	65.21% <ø> (ø)
banyand/metadata/server.go	48.93% <100.00%> (ø)
banyand/tsdb/shard.go	56.85% <100.00%> (+0.44%)	⬆️
banyand/tsdb/tsdb.go	53.93% <100.00%> (+0.56%)	⬆️
banyand/metadata/schema/node.go	7.69% <0.00%> (ø)
banyand/tsdb/block.go	50.91% <42.85%> (-0.21%)	⬇️
banyand/kv/kv.go	0.00% <0.00%> (ø)
pkg/index/inverted/inverted.go	69.46% <45.45%> (-0.27%)	⬇️
... and 10 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more