image/list: Add opt-in to --tree by default

[vvoland]

Add a new image-tree feature in ~/.docker/config.json which will make the docker image list use the new tree output by default.
The tree output is only used if no conflicting flag is passed (--format, --quiet, --digests, --no-trunc).

- Description for the changelog

`~/.docker/config.json` now supports an `image-tree` feature that will enable the new `image list` output by default whenever possible

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 28.57143% with 15 lines in your changes missing coverage. Please review.

Project coverage is 59.40%. Comparing base (17c5fe6) to head (37d8745).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5772      +/-   ##
==========================================
- Coverage   59.42%   59.40%   -0.03%     
==========================================
  Files         347      347              
  Lines       29402    29423      +21     
==========================================
+ Hits        17472    17478       +6     
- Misses      10958    10971      +13     
- Partials      972      974       +2     

[thaJeztah]

Hm, so my thinking with "enable by default" was to make the default a collapsed view of the tree-view, so that the columns stay the same (which is currently confusing, because without --tree you get different columns than with --tree); In that case, it would look something like this;

docker image ls
IMAGE                                            ID             DISK USAGE   CONTENT SIZE   IN USE
docker-cli-dev:latest                            743475d9ae54        817MB          192MB     ✔
myimage:latest                                   d4ac66306dd9       16.5MB         7.64MB
docker-dev:latest                                fb53cf31af0f       2.23GB          580MB     ✔
rpmbuild-fedora-41/arm64:latest                  347239e5d412       1.53GB          356MB
debbuild-ubuntu-noble/arm64:latest               07141bca479f       1.45GB          360MB
debbuild-debian-bookworm/arm64:latest            1c00b1e78af9       1.74GB          461MB
docker:cli                                       1624879c3635        260MB           66MB


docker image ls --tree
IMAGE                                            ID             DISK USAGE   CONTENT SIZE   IN USE
docker-cli-dev:latest                            743475d9ae54        817MB          192MB     ✔
└─ linux/arm64                                   9431815c64e4        817MB          192MB     ✔

myimage:latest                                   d4ac66306dd9       16.5MB         7.64MB
├─ linux/arm64                                   ec5b4b1cef2d       12.8MB         3.99MB
└─ linux/amd64                                   2bf9e92542e1       3.65MB         3.65MB

docker-dev:latest                                fb53cf31af0f       2.23GB          580MB     ✔
└─ linux/arm64                                   12a7c17e1b73       2.23GB          580MB     ✔

rpmbuild-fedora-41/arm64:latest                  347239e5d412       1.53GB          356MB
└─ linux/arm64                                   dd5275126098       1.53GB          356MB

debbuild-ubuntu-noble/arm64:latest               07141bca479f       1.45GB          360MB
└─ linux/arm64                                   032fb99f79b8       1.45GB          360MB

debbuild-debian-bookworm/arm64:latest            1c00b1e78af9       1.74GB          461MB
└─ linux/arm64                                   2b5c05517def       1.74GB          461MB

docker:cli                                       1624879c3635        260MB           66MB
├─ linux/amd64                                   e1b7fa9b2d15           0B             0B
├─ linux/arm/v6                                  67daf59d1ebd           0B             0B
├─ linux/arm/v7                                  ed7d82f74a17           0B             0B
└─ linux/arm64/v8                                311320051fb1        260MB           66MB

[thaJeztah]

☝️ However, that's where the discussion about these two PRs comes at hand;

• sorting the images alphabetically, because we no longer show a CREATED column, so the current sort-order does not correlate with anything that's visible; image ls --tree: order images alphabetically #5561
• considering each image:tag an entry in the list; even if the image:tag corresponds with another image:tag that happens to be refering to the same manifest image ls: show each tag for an image as a separate entry #5556

[vvoland]

Hmm right, I'll put it as draft for now.