test(core): add unit tests for merge trait

[pluveto]

Description

This update adds unit tests for the Merge trait implementations on BTreeMap, BTreeSet, Vec, and tuples. It also includes tests for the is_empty and take methods to ensure their correct functionality.

Notes to the Reviewers

• The tests cover basic scenarios for merging collections and checking their emptiness.
• Consider the potential method name conflict with BTreeSet's existing take method.

Changelog Notice

• Added unit tests for merging functionality and utility methods (is_empty, take) on various collection types.

Checklists

All Submissions:

• I've signed all my commits.
• I followed the contribution guidelines.
• I ran cargo fmt and cargo clippy before committing.

[LagginTimes]

Would it be valuable to include tests for conflict scenarios as well? For example:

let mut map1: BTreeMap<i32, &str> = BTreeMap::new();
map1.insert(1, "a");
let mut map2: BTreeMap<i32, &str> = BTreeMap::new();
map2.insert(1, "b");

map1.merge(map2);

assert_eq!(map1.len(), 1);
assert_eq!(map1.get(&1), Some(&"b"));

[pluveto]

I've added refactored empty check assertions and merge conflict tests. Squashed.

[evanlinjin]

ACK 871df7b

[LagginTimes]

ACK 665273d

[evanlinjin]

Great test additions. Here are some suggestions to make the tests more complete/easier to read.

[pluveto]

Indeed, that's more readable. Updated.

[evanlinjin]

Thanks for pushing forward on this. Let me know if you have any questions.

[pluveto]

Fixed and Rebased

[oleonardolima]

cACK a53f07b

[ValuedMammal]

ACK a53f07b may need a rebase to kick CI.

In a53f07b:

test: add tests for trait of operations on various data structures, including conflict scenarios and checking for empty structures

It would be better if the commit message stated that we're testing Merge.

[notmandatory]

Please rebase to pick up CI changes from #1803.

[notmandatory]

I did the rebase. :-)

Fixed here: #1738 (comment)