Refactor: remvoe Copy bound from NodeId

[drmingdrmer]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

Refactor: remvoe Copy bound from NodeId

The NodeId type is currently defined as:

type NodeId: .. + Copy + .. + 'static;

This commit removes the Copy bound from NodeId.
This modification will allow the use of non-Copy types as NodeId,
providing greater flexibility for applications that prefer
variable-length strings or other non-Copy types for node
identification.

This change maintain compatibility by updating derived Copy
implementations with manual implementations:

// Before
#[derive(Copy...)]
pub struct LogId<NID: NodeId> {}

// After
impl<NID: Copy> Copy for LogId<NID> {}

• Fix: Remove Copy Bound from NodeId #1250

---

This change is 

[SteveLauC]

Sorry for reviewing this PR on GitHub, reviewable does not show line numbers, which makes me impossible to locate the code and do a check in my IDE, left some comments.

BTW, there are multiple "unused" warnings reported by GitHub Actions on the review page, are they false-positive? If not, perhaps we can do a clean-up:)

[schreter]

@SteveLauC (no review from my side, just a tip)

reviewable does not show line numbers, which makes me impossible to locate the code and do a check in my IDE, left some comments

Actually, it does. It is just a bit cumbersome, since you have to set it up, see here. Similarly, for locating the code in the IDE, you can directly jump into the IDE from Reviewable from any comment (also from a new draft). It is documented here. With that, you don't even strictly need line numbers (BTW, those are shown in the draft of the new comment as well), but I personally did configure them for myself :-).

Reviewable status: 0 of 57 files reviewed, 4 unresolved discussions (waiting on @drmingdrmer and @SteveLauC)

[SteveLauC]

@SteveLauC (no review from my side, just a tip)

Amazing! TIL! Will set them up. 😄

[SteveLauC]

Reviewable status: 0 of 57 files reviewed, 4 unresolved discussions (waiting on @drmingdrmer)

[drmingdrmer]

@SteveLauC
Thank you for addressing these details. Your attention to these nuances is greatly appreciated.

@schreter
The Reviewable hints are indeed very helpful!

Unfortunately, I haven't figured out how to open CLion directly from Reviewable yet. My browser can open VS Code using the vscode:// protocol, but it doesn't work with clion:// for CLion.

I've learned that I need to manually register a URL handler for CLion. I'll try to set this up later. It's a bit disappointing that it's not as straightforward as with VS Code. :(