feat: Add varbit save-to-file

[pajlada]

This is enabled by default whenever you run RuneLite in developer mode

It saves files to the quest-helper directory in the RuneLite config directory (e.g. ~/.runelite/quest-helper/ on Linux)
Each launch creates its own file, formatted {unixtime}-varbits.txt (e.g. 1702671614895-varbits.txt)
The content of the files look like this:

[2023-12-16 00:44:38.813] [18951] VarPlayer 3079 changed: 502386 -> 502387
[2023-12-16 00:44:39.414] [18952] Varbit 12391 changed: 786 -> 387
[2023-12-16 00:44:39.414] [18952] Varbit 12392 changed: 38 -> 39
[2023-12-16 00:44:39.414] [18952] VarPlayer 3079 changed: 502387 -> 502388

I use this helper shell script to listening for changes in the most current varbit file:

#!/usr/bin/env bash

last_varbit_file="$(find . -type f -iname "*-varbits.txt" -exec ls -t1 {} + | head -1)"

ignores=(
    # Clan chat clock
    -e 'Varbit 8354 '

    # Chat interface size
    -e 'Varbit 5983 '

    # Fairy ring dialds
    -e 'Varbit 3985 '
    -e 'Varbit 3986 '
    -e 'Varbit 3987 '

    # HIDE_MINIMAP
    -e 'Varbit 542 '

    # Attack style
    -e 'VarPlayer 43 '

    # something to do with main hand weapon something
    -e 'VarPlayer 46 '

    # Equipped weapon attack style
    -e 'Varbit 357 '

    # ?? but they changes all the time
    -e 'Varbit 12391 '
    -e 'Varbit 12392 '
    # some league dialog thing
    -e 'Varbit 12393 '

    # Unknown but seems to change based off of attacking or getting attacked
    -e 'Varbit 5934 '

    # some regen timer
    -e 'VarPlayer 3079 '

    # some buff bar stuff
    -e 'VarPlayer 3078 '

    # Ignore all client-side things
    -e 'VarClientInt '
    -e 'VarClientStr '
)

tail -n 100 -f "$last_varbit_file" \
    | grep -v "${ignores[@]}"

I have it enabled-by-default since that's the best way to not forget to track things, and to ensure we actually track everything from start to finish.

Open questions

Should there be a setting to disable this functionality even in developer mode?
Should this even be enabled at all, or merged into the main repo at all? Or should developers working on quests just enable this by cherry-picking this commit or something

[pajlada]

This use case is now covered by the Action Logger plugin in the plugin hub