Refactor Application Settings and Support for Packaged/Unpackaged Mode #1924

[ghost1372]

This PR replaces the legacy ApplicationData-based settings system with a new SettingsHelper class. It adds support for both packaged and unpackaged app scenarios.

Closes #1924.

Old Settings System:

appData.LocalSettings.Values[SettingsKeys.IsLeftMode] = true;
New Settings System:

SettingsHelper.Current.IsLeftMode = true;

Note

Settings are automatically saved when changed.

Important Note on List Types:

Direct modification of list items won't persist changes:

SettingsHelper.Current.myList.Add(item); // ❌ This won't work

var list = SettingsHelper.Current.myList;
list.Add(item);
SettingsHelper.Current.myList = list; // ✅ This works

SettingsHelper Architecture:

Uses an ISettingsProvider abstraction.
In packaged mode: uses ApplicationDataContainer.
In unpackaged mode: uses JsonSettingsProvider.

Adding a New Setting:

public bool IsEnabled
{
    get => GetOrCreateDefault<bool>(true);
    set => Set(value);
}

Supported Types:

In unpackaged mode (JSON), you can serialize most types easily.

In packaged mode, ApplicationDataContainer supports only limited types directly:

• Primitives
• string
• DateTimeOffset
• TimeSpan
• Guid
• Windows.Foundation.Point
• Windows.Foundation.Size
• Windows.Foundation.Rect

Other types (e.g., decimal, List) are serialized to JSON before being stored.

Vector Types:

Types like Vector2, Vector3, and Vector4 do not work in regular mode. Instead, use wrapper classes like Vector2Data, Vector3Data, and Vector4Data:

public System.Numerics.Vector2 Position2D
{
    get => GetOrCreateDefault<Vector2Data>(new Vector2Data { X = 0, Y = 0 });
    set => Set((Vector2Data)value);
}