fix: centralize cache file registry

[mavonx]

What?

Replaces the hardcoded file list inside MigrateCacheFiles() with two package-level registries: cacheFiles for JSON cache files and cacheDirectories for cache subdirectories.

Why?

Previously, adding a new cache file to the project required finding and updating the hardcoded list inside MigrateCacheFiles(). This was easy to forget and caused files to be silently left behind in the old ~/.config/matcha/ location after migration. Now there is a single obvious place to register new cache paths.

Closes #564

[floatpanebot]

Benchmark report — no significant change

Metrics worse: 0 · better: 0 (threshold: ±3%).

benchstat output

goos: linux
goarch: amd64
pkg: github.com/floatpane/matcha/backend
cpu: AMD EPYC 7763 64-Core Processor                
                           │   old.txt    │                new.txt                │
                           │    sec/op    │    sec/op      vs base                │
ParseSearchQuery_Simple-4    2.620µ ± 30%   3.266µ ± 127%         ~ (p=0.485 n=6)
ParseSearchQuery_Complex-4   8.865µ ± 32%   8.266µ ±  74%         ~ (p=1.000 n=6)
TokenizeSearchQuery-4        3.585µ ± 86%   7.850µ ±  60%  +118.97% (p=0.041 n=6)
geomean                      4.367µ         5.962µ          +36.53%

                           │  old.txt   │              new.txt               │
                           │    B/op    │    B/op     vs base                │
ParseSearchQuery_Simple-4    26.00 ± 0%   26.00 ± 0%       ~ (p=1.000 n=6) ¹
ParseSearchQuery_Complex-4   762.0 ± 0%   762.0 ± 0%       ~ (p=1.000 n=6) ¹
TokenizeSearchQuery-4        176.0 ± 0%   176.0 ± 0%       ~ (p=1.000 n=6) ¹
geomean                      151.6        151.6       +0.00%
¹ all samples are equal

                           │  old.txt   │              new.txt               │
                           │ allocs/op  │ allocs/op   vs base                │
ParseSearchQuery_Simple-4    2.000 ± 0%   2.000 ± 0%       ~ (p=1.000 n=6) ¹
ParseSearchQuery_Complex-4   23.00 ± 0%   23.00 ± 0%       ~ (p=1.000 n=6) ¹
TokenizeSearchQuery-4        9.000 ± 0%   9.000 ± 0%       ~ (p=1.000 n=6) ¹
geomean                      7.453        7.453       +0.00%
¹ all samples are equal

pkg: github.com/floatpane/matcha/tui
                    │   old.txt    │              new.txt               │
                    │    sec/op    │    sec/op     vs base              │
LogPanelView-4        184.2µ ± 30%   172.7µ ± 13%       ~ (p=0.065 n=6)
SearchOverlayView-4   192.1µ ±  9%   195.3µ ± 11%       ~ (p=0.818 n=6)
InboxConstruction-4   1.043m ± 10%   1.032m ± 25%       ~ (p=0.818 n=6)
geomean               333.0µ         326.5µ        -1.94%

                    │    old.txt    │               new.txt               │
                    │     B/op      │     B/op       vs base              │
LogPanelView-4        44.67Ki ± 51%   44.67Ki ± 51%       ~ (p=1.000 n=6)
SearchOverlayView-4   44.67Ki ± 26%   56.14Ki ± 41%       ~ (p=0.416 n=6)
InboxConstruction-4   874.2Ki ±  0%   874.3Ki ±  0%       ~ (p=0.457 n=6)
geomean               120.4Ki         129.9Ki        +7.91%

                    │   old.txt   │              new.txt              │
                    │  allocs/op  │  allocs/op   vs base              │
LogPanelView-4         714.0 ± 0%    714.0 ± 0%       ~ (p=1.000 n=6)
SearchOverlayView-4    925.0 ± 0%    926.0 ± 0%       ~ (p=0.340 n=6)
InboxConstruction-4   3.478k ± 0%   3.478k ± 0%       ~ (p=0.716 n=6)
geomean               1.319k        1.320k       +0.04%

_{auto-generated by benchmarks.yml}

[mavonx]

@andrinoff

Please mark this PR as draft temporarily. I noticed the same thing needs to be refactored in some other places as well.

[andrinoff]

@mavonx you can and should convert yourself

[mavonx]

@andrinoff

Ready for review.

[andrinoff]

@mavonx join the Discord, please, we communicate there, there is also an audit log

[andrinoff]

collectDataFiles still has the directory names hardcoded (also in bodyDir and sigDir) loop over them too