[DDW-920] RTS flags UI/UX improvements

[marcin-mazurek]

This PR improves the UX of RTS flags settings as per designs: https://app.zeplin.io/project/57acfaa7436a750316161a8b/screen/61eacc759584d057bbdf916c

Screenshots

When enabling/disabling top menu

Recommendation shown only once

Diagnostics screen

Testing Checklist

• Slack QA thread
• Test

---

Test Scenarios

Scenario 1 - Validate initial warning

Given that Daedalus was just installed on a clean state
And it's running on a low spec system (<16 GB RAM)
When I complete the initial setup
Then I can see a warning that reads the following:

- EN: REMINDER: You are running Daedalus with less memory than recommended and might experience a slow syncing time.You can enable RAM management (RTS Flags), an experimental setting that can reduce memory usage on computers with less than 16GB of RAM.


- JP: 警告/リマインダー：Daedalusは現在推奨値未満のメモリーで実行されています。パフォーマンスを改善するためにこの試験的設定を試すことができます。

And upon closing it or clicking "Decide later" it is not displayed again

Scenario 2 - Enable RTS flags on initial warning

Given that Daedalus was just installed on a clean state
And it's running on a low spec machine (<16 GB)
When I complete the initial setup
Then I can see a warning that suggests enabling RTS flags
And upon clicking on "Enable and quit" Daedalus closes
When I open Daedalus manually again
Then the RTS flags are enabled

Scenario 3 - Validate RTS flags dialog (disabled)

Given that Daedalus is running
And RTS flags are disabled
When I access to Help - Using RTS flags
Then I can see a dialog that reads the following

- EN: When enabled, the Cardano node will attempt to reduce its RAM usage. You will need to restart Daedalus for this change to take effect.


- JP: 有効にすると、CardanoノードはRAM使用量の削減を試みます。変更を有効にするために、Daedalusを再起動する必要があります。

Scenario 4 - Validate RTS flags dialog (enabled)

Given that Daedalus is running
And RTS flags are enabled
When I access to Help - Using RTS flags
Then I can see a dialog that reads the following

- EN: When disabled, the Cardano node will start in default mode. You will need to restart Daedalus for this change to take effect.


- JP: 無効にすると、Cardanoノードはデフォルトモードで起動します。変更を有効にするために、Daedalusを再起動する必要があります。

Scenario 5 - Enable RTS flags

Given that I am on the "RTS flags" dialogs
And RTS flags are disabled
When I click on "Enable and quit"
Then I can see Daedalus closes
And after I open it manually again, the RTS flags are enabled

Scenario 6 - Disable RTS flags

Given that I am on the "RTS flags" dialogs
And RTS flags are enabled
When I click on "Disable and quit"
Then I can see Daedalus closes
And after I open it manually again, the RTS flags are disabled

Scenario 7 - Validate RTS status on Diagnostics screen

Given that I am on the "Diagnostic screen"
When I validate the system info
Then I can see there is an item that indicates the status of RTS flags (ON/OFF)
And the information matches the current status on RTS flags on this instance of Daedalus

Scenario 8 - Validate RTS status on Diagnostics screen (low spec)

Given that I am on the "Diagnostic screen"
And I am running on a low spec system (<16 GB RAM)
When I validate the system info
Then I can see there is an item that indicates if the recommended system requirements are not met (Low)

Scenario 9 - Validate RTS status on Diagnostics screen (high spec)

Given that I am on the "Diagnostic screen"
And I am running on a high spec system (>=16 GB RAM)
When I validate the system info
Then I can see there is an item that indicates if the recommended system requirements are met (Good)

Scenario 10 - Validate RTS flags overlay (RTS disabled)

Given that Daedalus is closed
And I'm on a low spec machine (<16 GB RAM)
And RTS flags weren't enabled on Daedalus
When I run Daedalus
Then I can see a warning that suggests enabling RTS flags

Scenario 11 - Validate RTS flags overlay (RTS enabled)

Given that Daedalus is closed
And I'm on a low spec machine (<16 GB RAM)
And RTS flags are enabled on Daedalus
When I run Daedalus
Then I can see no warning is displayed

---

Review Checklist

Basics

• PR assigned to the PR author(s)
• input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
• If there are UI changes, Alexander Rukin assigned as an additional reviewer
• PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
• PR link is added to a Jira ticket, ticket moved to In Review
• PR is updated to the most recent version of the target branch (and there are no conflicts)
• PR has a good description that summarizes all changes
• PR contains screenshots (in case of UI changes)
• CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
• There are no missing translations (running yarn manage:translations produces no changes)
• Text changes are proofread and approved (Jane Wild / Amy Reeve)
• Japanese text changes are proofread and approved (Junko Oda)
• Storybook works and no stories are broken (yarn storybook)
• In case of dependency changes yarn.lock file is updated

Code Quality

• Important parts of the code are properly commented and documented
• Code is properly typed with flow
• React components are split-up enough to avoid unnecessary re-renderings
• Any code that only works in main process is neatly separated from components

Testing

• New feature/change is covered by acceptance tests
• New feature/change is manually tested and approved by QA team
• All existing acceptance tests are still up-to-date
• New feature/change is covered by Daedalus Testing scenario
• All existing Daedalus Testing scenarios are still up-to-date

After Review

• Update Slack QA thread by marking it with a green checkmark

[marcin-mazurek]

Requirement from @alexander-rukin

[gabriela-ponce]

Looks good. Will approve once translations are ready 👍