feat: add toggle support for sort boolean flags

[alastairsounds]

Resolves #3157

Rationale

sort's boolean flags (--reverse, --dir-first, --translit) had no toggle support. This adds toggle as a valid value for each, mirroring the existing hidden toggle command.

sort --reverse=toggle
sort --dir-first=toggle
sort --translit=toggle

Changes

• yazi-parser: Adds SortBoolState enum (none / on / off / toggle), replacing bool for the three flags. Modelled on HiddenOptState.
• yazi-actor: Sort actor now calls .bool(old) so none preserves and toggle inverts current state.

[alastairsounds]

Also wondering if I should implement this for the sensitive sort? But figure there's a little less utility in toggling case sensitivity 🤷🏻‍♂️

[sxyazi]

This treats both boolean and string as SortBoolState, but it isn't clear whether SortBoolState should be serialized as a boolean or a string in Lua, which was in use by https://yazi-rs.github.io/docs/tips#folder-rules

[alastairsounds]

I see what you're saying. I think it should be serialized as a boolean and not handle strings. I don't see a scenario in which a user would need to set "toggle" via a Lua script. Since it's not really a "state" per-se, I've updated Sort::hook() to account for that. Now, when any of reverse, dir_first, or translit contains Toggle, it returns None to skip preflight entirely.

https://github.com/sxyazi/yazi/pull/3777/changes#diff-608cad97a235673889398f55a252b08703746ca6bce53ee32ebaabe78294f9cbR62-R70

With this revision, Lua shouldn't be able to see "toggle". Sorts that occur from plugins should work normally since they're only handling booleans and not strings.

Toggle being a CLI feature, not Lua, seems like a clean implementation. Or might there be a better route to follow?