btree: add {Entry,VacantEntry}::insert_entry

[cuviper]

This matches the recently-stabilized methods on HashMap entries. I've
reused tracking issue #65225 for now, but we may want to split it.

[rustbot]

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[ibraheemdev]

r? libs-api for new unstable API surface

[cuviper]

FWIW, I'm also working on a BTreeSet entry API to match HashSet's, and insert_entry will come in handy. I could still create and use that internally, but I don't see why we shouldn't expose it publicly as well.

[Amanieu]

Not 100% sure about the lifetime magic in the BTreeMap internals, but if it passes Miri then it's probably fine.

@bors r+

[bors]

📌 Commit 584ec95 has been approved by Amanieu

It is now in the queue for this repository.

[cuviper]

Not 100% sure about the lifetime magic in the BTreeMap internals, but if it passes Miri then it's probably fine.

Yeah, it's hairy, but it does pass Miri for me. I hope that coverage is good enough, given that I also modified VacantEntry::insert to use the new code, and that's used by the main BTreeMap::insert too.