Module-specific options not persisting - implement option memory with .trainer file integration

[saveli]

Problem

Module-specific options are not being saved between sessions, requiring users to frequently
reconfigure the same options. This creates a poor user experience when working with modules
repeatedly.

Proposed Solution

Implement option persistence by:

1. Save changes to .trainer file: When users modify module-specific options, automatically
   save these changes to the corresponding .trainer file. The first element in the option
   string should remain the default value.

2. Make behavior configurable: Expose this persistence behavior as an environment variable
   that can be edited in the .env file, allowing users to enable/disable this feature as
   needed.

Implementation Details

• Identify where module-specific options are currently handled
• Implement logic to save user-selected options to .trainer files
• Ensure the first element in option strings remains the default value
• Add environment variable to control this behavior (e.g.,
  SAVE_MODULE_OPTIONS=true/false)
• Update .env file template with the new configuration option
• Test that options are properly restored on subsequent module loads

Acceptance Criteria

• Users' last-selected options are remembered between sessions
• The feature can be toggled via environment variable
• Default values are preserved in .trainer files
• No breaking changes to existing functionality

Priority

Enhancement - improves user experience by reducing repetitive configuration tasks