[Collections\dictionary] Migrate tests to unitt

[RickBarretto]

Description

Migrate print based tests to unitt, decoupling dictionary behavior from print function.

• Ref.: [Collections] Refactoring Collections #1786

Type of change

• Code cleanup
• Unit tests (added or updated unit-tests)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (implementation update, or general performance enhancements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (documentation-related additions)

[drkameleon]

Ready to merge! 🚀

[RickBarretto]

@drkameleon if you need me to push some random commit to rerun the CI, let me know. 😉

[drkameleon]

@drkameleon if you need me to push some random commit to rerun the CI, let me know. 😉

I had totally missed this one. And I have absolutely zero idea why the CI actions are stuck... Can you merge from the master and just commit/push?

[drkameleon]

@RickBarretto Ping! lol 😄

[RickBarretto]

@RickBarretto Ping! lol 😄

@drkameleon Do you want me to push a random commit?

I've finished this PR. And also, I'm using the older version of unitt.

[drkameleon]

@RickBarretto Ping! lol 😄

@drkameleon Do you want me to push a random commit?

I've finished this PR. And also, I'm using the older version of unitt.

Yes, I think this could work. 😉 I mean, it's literally stuck like that lol

[RickBarretto]

@drkameleon alright, I'll push ASAP when I touch my computer.
I'll do this today at night. 😉

[drkameleon]

@RickBarretto In the end, I added a trivial commit myself to get it... rolling, but it appears it stumbles upon an error in the unit-test itself 🤔

Can you have a look into it so that we can merge it? 😉