show object kind, name and address when using dbg!

[jasonwilliams]

This should implement Debug a bit better for objects, previously they recursed a lot and spewed out a lot of garbage. This shows the kind, name and address for each object, which should be enough when investigating issues.

Before:

After:
&func = (Function) "fib" 0x7F9A67F17218

[codecov]

Codecov Report

Merging #2960 (efbd36b) into main (65bf54d) will decrease coverage by 0.12%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##             main    #2960      +/-   ##
==========================================
- Coverage   50.22%   50.11%   -0.12%     
==========================================
  Files         446      446              
  Lines       46019    46027       +8     
==========================================
- Hits        23114    23065      -49     
- Misses      22905    22962      +57     

Impacted Files	Coverage Δ
boa_engine/src/object/jsobject.rs	55.31% <41.66%> (-3.08%)	⬇️

... and 7 files with indirect coverage changes

[HalidOdat]

Looks good! Check the comment to see how we might improve it :)

[HalidOdat]

Looks good to me! :)

Just need to run rust-fmt

[jedel1043]

Thanks! This should significantly improve the output of dbg!.

[jasonwilliams]

I can do this in a follow up or but I left the recursion stuff in there, I gues that can be removed as it’s not possible for recursion when printing a object now (unless we want to improve the output later on with properties etc)

@HalidOdat @raskad

[jedel1043]

I can do this in a follow up or but I left the recursion stuff in there, I gues that can be removed as it’s not possible for recursion when printing a object now (unless we want to improve the output later on with properties etc)

While debugging I tend to use object.display().internals(true) more. This change should mostly benefit end users since it won't spit pages and pages of properties while asserting that two values are equal, for example. I think we should remove the recursion.