chore: specify binary name

[WenyXu]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

Each fuzz test will add a new binary target. Therefore, we should specify the binary name in Cargo build.

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.

[tisonkun]

Each fuzz test will add a new binary target. Therefore, we should specify the binary name in Cargo build.

I don't get it clearly. Could you elaborate a bit? Is the binary redundant or wrong? Could you attract some logs to explain the case?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.03%. Comparing base (5d644c0) to head (f20ee83).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3449      +/-   ##
==========================================
- Coverage   85.44%   85.03%   -0.41%     
==========================================
  Files         895      895              
  Lines      147091   147118      +27     
==========================================
- Hits       125680   125102     -578     
- Misses      21411    22016     +605     

[MichaelScofield]

@tisonkun I think what @WenyXu trying to achieve here is to reduce some unnecessary bin builds.

[tisonkun]

Got it. We're reducing unnecessary binary build like fuzz target here ..