Fixes #408

The main cause of this flicker is the long delay between the value changes of Checkbox::IsChecked and Checkbox::IsEnabled properties.

This is due to how the calculator generates the 64 different AutomationProperties::Name values and how the app converts the number in enumerable. These 2 tasks were too CPU-intensive for no reason.

Description of the changes:

• Optimize how we convert the binary number into a list of booleans:
  • Before:
    • In VM: call GetStringForDisplay, GroupDigitsPerRadix (add spaces), localizer.LocalizeDisplayValue (convert '0', '1' into the local equivalents)
    • In View: remove LTR, RTL, spaces, etc... , remove characters added by LocalizeDisplayValue, add padding ('0'), compare each characters with the local '0'
  • Now:
    • In VM: call GetStringForDisplay, convert the string in vector
    • in View: nothing
• remove the very heavy and not optimized BitFlipAutomationNameConverter converter and replace it by a lighter and more optimized way to generate strings (note: this converter was called 64 times every time the number was changed or the bit length changed)
• Create new type BitLength and use only one way to represent bit lengths in CopyPasteManager, StandardCalculatorViewModel (instead of 4 booleans + 1 enum)
• The view model is now responsible for sending commands to CalculatorManager instead of the view.
• optimize CalculatorProgrammerBitFlipPanel
  • remove half of native bindings
  • modify how the application manages the visibility of this control

How changes were validated:

• Tested in all modes

Result

• CPU usage decreased when users enter a new number or change bit length
• No more flickering