Improve consistency/clarity by moving the remaining session-agnostic KV-persisted toggles to the System category

[ariane-emory]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

At this point in time, some of the items in the command palette the toggle the states of options related to hiding or showing elements or changing their appearance, that are persistent to the kv.json file, and that persist across sessions live in the System subgroup of the command palette while some live in the the Session subgroup:

Items that are already in the System group

• Disable/Enable animations
• Disable/Enable diff wrapping
• Toggle appearance

Items that languish in the Session group

• Show/Hide timestamps
• Show/Hide thinking
• Show/Hide tool details
• Show/Hide header

For consistency and clarity, the items that are currently located in the session group ought be moved to the system group for these reasons:

• Their current placement is deceptive: none of these options relate to or affect the current session specifically, and as they are persisted to the KV file, their state persists through session boundaries (such as the execution of a /new command or a restart of OpenCode).
• In the vast majority of cases, consistency is preferable to inconsistency.

My conclusion:

To achieve consistency and gain clarity, these four items listed above that are located in the Session group ought to be moved to the System group, and ought to be available for use before sending a message and beginning a session.