Refactor SetConstant to use a lookup table

[RealRanger]

The current implementation of ProfileStore.SetConstant relies on a long if/else chain to assign values. While it works, this approach:

• Is verbose and harder to maintain
• Increases the risk of typos

Solution

Refactored ProfileStore.SetConstant to use a private lookup table (_constantSetters) scoped in ProfileStore.

• Each constant name maps to a setter function that updates the corresponding constant.
• The rest of the codebase still used the same global constants; no breaking changes.
• New constants only require one new line in the lookup table.

Benefits

• Cleaner, more maintainable code
• Reduced risk of errors when expanding or changing the constants set