Recent Commits to kint:master

Various missing tests, coverage stuff

CallFinder: Add meta info for when new without parens is used

MethodValue rewrite

This allows us to squeeze a lot more perf out of complex systems
by omitting the access paths and depth. Effectively we can avoid
cloning all methods for every instance and just reuse the existing
MethodValues repeatedly.

Totally incompatible with text renderers since they pretty much
require depth to be set correctly

SplFileInfoRepresentationTest: Fixup

TabPluginInterface: Send value along with representation

CSS: Rename --color-size to --nav-size

It's the element that decides the height of the bar, so we
shouldn't go beyond the nav in height

Small CSS fixups

* Solarized actually names its colors 03, 02, 01, 00, 0, 1, 2, 3
  so those leading digits are actually relevant.
* It turns out .kint-trace hasn't been a thing since kint 1 back
  in 2016 (Wow)
* I'm very glad that highlight color has been broken all this
  time, it's horrible. Scrapped
* The problem with the color preview box is that you can change
  the width and height, so setting a max doesn't actually solve
  the underlying issue. It's just hard to get the checker pattern
  to line up with the box it's in even if you know the dimensions.

migrate from scss variables to css vars instead

CallFinder: Better literal detection

Before we'd just check if strings matched `"..."` to say it was a
literal which incorrectly made things like `"$a"` out to be literals

This also fixed an edge case with non-literal PHP6 style strings
like `b"$a"` incorrectly not incrementing depth

CallFinder: More perf improvements

TextRenderer::renderHeader: Small cleanup

SplFileInfoValue::getDisplayValue: Return short path

Rename Kint::$app_root_dirs to Utils::$path_aliases

Call Utils::shortenPath now instead of Kint::shortenPath

Move file_link_format to AbstractRenderer

HtmlPluginTest: Coverage fix

SimpleXML: Standardize string handling

Since SimpleXMLElements can be cast to string there's always been
this question of "Should I treat the SimpleXMLElement itself as a
string?" which leads to 2 scenarios:

1.  The string contents are a separate value in a toString
    representation, adding a level of depth. This is confusing
    because the string and the element will have the same name.
2.  Both the attributes, the string contents, and any string
    representations like JSON have to be on the same element,
    which saves depth but can lead to even more confusion.

I decided to go with 1. To fix the confusion between the two values
I set the access path of SimpleXMLElements back to the element's
own access path and change the name of the string value instead.

Before:
Name: y
Path: (string) $x->y
Child:
  Name: y
  Path: (string) $x->y

After:
Name: y
Path: $x->y
Child:
  Name: (string) y
  Path: (string) $x->y

DomPlugin: Put classList iterator first

Merge dom plugins

CallFinder: PHP 8.2+ performance optimization