refactor(component editor): Use the new data-model class

Also adds many pytests
Updates the architecture documentation

Author: amilcarlucas

ARCHITECTURE.md

@@ -155,58 +155,90 @@ We decided to use python as programming language, and the following libraries an
 - [tkinter](https://docs.python.org/3/library/tkinter.html) for the graphical user interface
 - GNU gettext `po` files to translate the software to other languages
 
-To satisfy the system design requirements described above the following five sub-applications were developed:
+The (main) application itself does the command line parsing and starts the sub-applications defined below in sequence
+
+- [`__main__.py`](ardupilot_methodic_configurator/__main__.py)
+
+To satisfy the system design requirements described above the following five user interface sub-applications were developed:
 
 - **check for software updates**
   - checks if there is a newer software version available, downloads and updates it
+  - [`frontend_tkinter_software_update.py`](ardupilot_methodic_configurator/frontend_tkinter_software_update.py)
 - **FC communication**
   - establishes connection to the flight controller, gets hardware information, downloads parameters and their default values
+  - [`frontend_tkinter_connection_selection.py`](ardupilot_methodic_configurator/frontend_tkinter_connection_selection.py)
+    - [`frontend_tkinter_flightcontroller_info.py`](ardupilot_methodic_configurator/frontend_tkinter_flightcontroller_info.py)
 - **choose project to open**
   - either creates a new project or opens an existing one, downloads parameter documentation metadata corresponding to the FC firmware version to the project directory
+  - [`frontend_tkinter_directory_selection.py`](ardupilot_methodic_configurator/frontend_tkinter_directory_selection.py)
+    - [`frontend_tkinter_template_overview.py`](ardupilot_methodic_configurator/frontend_tkinter_template_overview.py)
 - **define vehicle components and their connections**
   - define specifications of all vehicle components and their connections to the flight controller
+  - [`frontend_tkinter_component_editor.py`](ardupilot_methodic_configurator/frontend_tkinter_component_editor.py)
+    - [`frontend_tkinter_component_editor_base.py`](ardupilot_methodic_configurator/frontend_tkinter_component_editor_base.py)
+    - [`frontend_tkinter_component_template_manager.py`](ardupilot_methodic_configurator/frontend_tkinter_component_template_manager.py)
 - **view documentation, edit parameters, upload them to FC**
   - sequentially for each configuration step:
     - view documentation relevant for the current configuration step,
     - edit parameters relevant for the current configuration step,
     - upload them to the flight controller,
     - save them to file
+  - [`frontend_tkinter_parameter_editor.py`](ardupilot_methodic_configurator/frontend_tkinter_parameter_editor.py)
+    - [`frontend_tkinter_parameter_editor_documentation_frame.py`](ardupilot_methodic_configurator/frontend_tkinter_parameter_editor_documentation_frame.py)
+    - [`frontend_tkinter_parameter_editor_table.py`](ardupilot_methodic_configurator/frontend_tkinter_parameter_editor_table.py)
+    - [`frontend_tkinter_stage_progress.py`](ardupilot_methodic_configurator/frontend_tkinter_stage_progress.py)
 
 Each sub-application can be run in isolation, so it is easier to test and develop them.
 
+The data models. Each application separates the business logic from the user interface logic.
+This improves testability and maintainability of the code.
+
+1. Check for software updates:
+   1. [`middleware_software_updates.py`](ardupilot_methodic_configurator/middleware_software_updates.py)
+1. FC connection:
+   1. [`middleware_fc_ids.py`](ardupilot_methodic_configurator/middleware_fc_ids.py) <- autogenerated by `update_flight_controller_ids.py`
+1. Component editor:
+   1. [`battery_cell_voltages.py`](ardupilot_methodic_configurator/battery_cell_voltages.py)
+   1. [`data_model_vehicle_components_base.py`](ardupilot_methodic_configurator/data_model_vehicle_components_base.py)
+   1. [`data_model_vehicle_components_import.py`](ardupilot_methodic_configurator/data_model_vehicle_components_import.py)
+   1. [`data_model_vehicle_components_templates.py`](ardupilot_methodic_configurator/data_model_vehicle_components_templates.py)
+   1. [`data_model_vehicle_components_validation.py`](ardupilot_methodic_configurator/data_model_vehicle_components_validation.py)
+   1. [`data_model_vehicle_components.py`](ardupilot_methodic_configurator/data_model_vehicle_components.py)
+
 All applications use one or more of the following libraries:
 
 1. internationalization
    1. [`__init__.py`](ardupilot_methodic_configurator/__init__.py)
-   2. [`internationalization.py`](ardupilot_methodic_configurator/internationalization.py)
+   1. [`internationalization.py`](ardupilot_methodic_configurator/internationalization.py)
+   1. [`configuration_steps_strings.py`](ardupilot_methodic_configurator/configuration_steps_strings.py) <- autogenerated by `update_configuration_steps_translation.py`
+   1. [`vehicle_components.py`](ardupilot_methodic_configurator/vehicle_components.py) <- autogenerated by `update_vehicle_components_translation.py`
 1. command line parsing
    1. [`common_arguments.py`](ardupilot_methodic_configurator/common_arguments.py)
+   1. [`argparse_check_range.py`](ardupilot_methodic_configurator/argparse_check_range.py)
 1. the local filesystem backend does file I/O on the local file system. Operates mostly on parameter files and metadata/documentation files
    1. [`backend_filesystem.py`](ardupilot_methodic_configurator/backend_filesystem.py)
    2. [`backend_filesystem_vehicle_components.py`](ardupilot_methodic_configurator/backend_filesystem_vehicle_components.py)
    3. [`backend_filesystem_configuration_steps.py`](ardupilot_methodic_configurator/backend_filesystem_configuration_steps.py)
+   4. [`backend_filesystem_program_settings.py`](ardupilot_methodic_configurator/backend_filesystem_program_settings.py)
 1. the internet backend communicates with the internet
    1. [`backend_internet.py`](ardupilot_methodic_configurator/backend_internet.py)
 1. the flight controller backend communicates with the flight controller
    1. [`backend_flightcontroller.py`](ardupilot_methodic_configurator/backend_flightcontroller.py)
    2. [`backend_mavftp.py`](ardupilot_methodic_configurator/backend_mavftp.py)
-   3. [`battery_cell_voltages.py`](ardupilot_methodic_configurator/battery_cell_voltages.py)
 1. the tkinter frontend, which is the GUI the user interacts with
+   1. [`frontend_tkinter_autoresize_combobox.py`](ardupilot_methodic_configurator/frontend_tkinter_autoresize_combobox.py)
    1. [`frontend_tkinter_base_window.py`](ardupilot_methodic_configurator/frontend_tkinter_base_window.py)
-   2. [`frontend_tkinter_connection_selection.py`](ardupilot_methodic_configurator/frontend_tkinter_connection_selection.py)
-   3. [`frontend_tkinter_directory_selection.py`](ardupilot_methodic_configurator/frontend_tkinter_directory_selection.py)
-   4. [`frontend_tkinter_component_editor.py`](ardupilot_methodic_configurator/frontend_tkinter_component_editor.py)
-   5. [`frontend_tkinter_component_editor_base.py`](ardupilot_methodic_configurator/frontend_tkinter_component_editor_base.py)
-   6. [`frontend_tkinter_parameter_editor.py`](ardupilot_methodic_configurator/frontend_tkinter_parameter_editor.py)
-   7. [`frontend_tkinter_parameter_editor_table.py`](ardupilot_methodic_configurator/frontend_tkinter_parameter_editor_table.py)
-
-The (main) application itself does the command line parsing and starts the other sub-applications in sequence
-
-- [`__main__.py`](ardupilot_methodic_configurator/__main__.py)
+   1. [`frontend_tkinter_entry_dynamic.py`](ardupilot_methodic_configurator/frontend_tkinter_entry_dynamic.py)
+   1. [`frontend_tkinter_pair_tuple_combobox.py`](ardupilot_methodic_configurator/frontend_tkinter_pair_tuple_combobox.py)
+   1. [`frontend_tkinter_progress_window.py`](ardupilot_methodic_configurator/frontend_tkinter_progress_window.py)
+   1. [`frontend_tkinter_rich_text.py`](ardupilot_methodic_configurator/frontend_tkinter_rich_text.py)
+   1. [`frontend_tkinter_scroll_frame.py`](ardupilot_methodic_configurator/frontend_tkinter_scroll_frame.py)
+   1. [`frontend_tkinter_show.py`](ardupilot_methodic_configurator/frontend_tkinter_show.py)
+   1. [`frontend_tkinter_usage_popup_window.py`](ardupilot_methodic_configurator/frontend_tkinter_usage_popup_window.py)
 
 When all is combined it looks like this:
 
-![Software Architecture diagram](images/Architecture.drawio.png)
+![Software Architecture diagram](images/Architecture2.drawio.png)
 
 The parts can be individually tested, and do have unit tests.
 They can also be exchanged, for instance, [tkinter-frontend](https://docs.python.org/3/library/tkinter.html) can be replaced with