feat(remote_wal): append a noop record after kafka topic initialization

[WenyXu]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

Append a noop record after kafka topic initialization.

If the EntryId starts from 0, then the first entry in the mito engine will be dropped after restart. The mito always replays the memtable from the flushed id + 1(i.e., 0+1=1). Therefore, The EntryId must start from 1.

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR does not require documentation updates.

Refer to a related PR or issue link (optional)

close #3039

[codecov]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (7152407) 85.50% compared to head (e0397c8) 85.04%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3040      +/-   ##
==========================================
- Coverage   85.50%   85.04%   -0.46%     
==========================================
  Files         793      793              
  Lines      128447   128481      +34     
==========================================
- Hits       109825   109264     -561     
- Misses      18622    19217     +595     

[niebayes]

non-blocking: We might need to get the LEO before producing a no-op record. Or there will be one no-op record each time the metasrv starts.

For LEO, refer to this

[fengjiachun]

LGTM