Edit Config Journey - Improvement to allow navigation to specific steps in the installer

[zimaah]

User Story

As a node operator, I want to be able to choose what part of the configuration I'll edit (sub-chain name, channels, etc) rather than navigating through all steps in the journey just to edit a specific part.

Description

We need to provide a menu to the node operator, so he can click and jump straight to the part of the configuration that he wants to edit. This menu will be shown when the node operator clicks in the "edit chain" button in the Settings/Chains page. Once the node operator lands on the specific part of the configuration, he will be able to edit it, re-open the menu to navigate to a diff step or navigate back to the Settings/Chains page.

Requirements

• Open a modal with 5 buttons/links when the node operator clicks in the "edit chain" button in the data-table present at Settings/Chains page
• Each page in the installer (sub-chain, channels, etc) must be updated to cater for the edit journey
  • We need a "Back to Settings" button, which will take the node operator back to the Settings/Chains page
  • We need a "Open menu" button, which will open the nav menu (same as we show when the node operator clicks in the "edit" button in the data-table). It will enable the node operator to navigate to specific parts of the configuration without having to go back/forward over all steps.

Acceptance criteria

Scenario: Chain config edit
Given: The node operator is editing a chain
When: He clicks in the "edit" button in the data table
And: A modal is shown with 5 buttons/links, each representing a diff part of the config journey
And: He clicks in one of the options
Then: The specific page in the installer is loaded and from there he can edit that part of the config, navigate back to Settings/Chains or navigate to a diff page in the installer.

[zimaah]

Extra requirement caught while reviewing the MR

• Currently, the ready config flag is set to true only when the node operator actually finishes the configuration journey (aka goes to the last step - Alerts - and clicks in the finish button. This might not always be the case, since the node operator can leave the installer by clicking in the browser button. If he does that, then he will see a "valid" config (but with ready=false) in the data-table displayed at Settings/Chains. We need to come up with a solution to delete configs with ready=false if the node operator leaves the installer journey without finishing it properly.