feat(message-system): add ab testing message

[adderpositive]

Description

• Experiments would use a Message System to configure Feature Flags (i.e. there will be no UI to config experiments, deployment of the messaging system will be required - independent from Suite release though).
• Experiment ID (e.g. rename-trade-section)
  • Multiple Variation IDs (e.g. control, buy-swap) - this may be unlimited, but in reality, we won’t use more than 4 for one experiment
  • Each would have an experiment distribution percentage between 0 - 100%

Example of experiments

experiments property is placed in the top level of config.v[version].json

  "experiments": [
      {
          "conditions": [
              {
                  "environment": {
                      "desktop": ">=24.5.1",
                      "mobile": "!",
                      "web": ">=24.5.1"
                  }
              }
          ],
          "experiment": {
              "id": "3bed56a4-ecd8-4e0f-2910-014b484c2aff",
              "groups": [
                  {
                      "variant": "A",
                      "percentage": 30
                  },
                  {
                      "variant": "B",
                      "percentage": 70
                  }
              ]
          }
      }
  ]

• conditions are the same property as for the action - https://github.com/trezor/trezor-suite/blob/develop/docs/features/message-system.md
• experiment has required parameters id and groups
  • id must be unique, but can also be used for nice naming (e.g. "button-testing")
  • groups as an array of testing groups - minimum length of items is two
    • percentage is a number between 0 and 100, a sum of all percentages has to be 100
    • variant can be any string - name of the group
• updated documentation - https://github.com/trezor/trezor-suite/blob/feat/ab-testing-on-message-system/docs/features/message-system.md

Related Issue

Resolve #15279
Resolve #15067

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 10
• More info

Learn more about 𝝠 Expo Github Action

[MiroslavProchazka]

Hello @adderpositive , please let's wait for @tomasklim and let's discuss this in more broader context. Personally I do not like the idea to mix it with message system, so lets discuss.

[adderpositive]

Hello @adderpositive , please let's wait for @tomasklim and let's discuss this in more broader context. Personally I do not like the idea to mix it with message system, so lets discuss.

Yes, of course. We have been already discussing the extension of the system. I will go ahead and briefly describe it here.

1. The first solution was implemented directly into the message-system messages. After brainstorming, I have refactored it to the solution in the PR.
2. The next solution is to rename the system - message-system can be confusing if it manages more functionality than messages only. Examples of some names toggle-system, push-system, ...
3. But @matejkriz had an excellent point of view the message system should provide a solution how to safely and unforgettably deliver a message to the Suite at runtime - the message can be distinguished as banner, feature or experiment, etc. It is different than it should display only some messages.

I hope it is understandable a little bit. :)