feat: Add import configuration command for JSON files

- Introduced a new command `import-config` to import various configuration files (Flow Manager, RBAC Manager, Backoffice, Fast Data, API Console) into a Mia-Platform project.
- Created example configuration files for Flow Manager, RBAC Manager, Fast Data, and Extensions.
- Implemented file validation and JSON reading functions to ensure proper configuration structure.
- Added confirmation prompt before executing the import to prevent accidental changes.
- Developed unit tests to validate the functionality of the import command and its components.

Author: daniele.cina

docs/30_commands.md

@@ -624,6 +624,36 @@ Available flags for the command:
 - `--context`, to specify a different context from the currently selected one
 - `--company-id`, to set the ID of the desired Company
 
+### import-config
+
+The `project import-config` subcommand allows you to import specific configuration files in a Mia-Platform Console project.
+This command can be used to import one or more configuration files at the same time.
+
+Usage:
+
+```sh
+miactl project import-config [flags]
+```
+
+Available flags for the command:
+
+- `--revision`, to specify the revision of the commit to import the configuration (mutually exclusive with --environment)
+- `--environment`, to specify the environment where to import the configuration (mutually exclusive with --revision)
+- `--flow-manager-config`, path to the flowManagerConfig.json file
+- `--rbac-manager-config`, path to the rbacManagerConfig.json file
+- `--backoffice-config`, path to the backofficeConfigurations.json file
+- `--fast-data-config`, path to the fast-data-config.json file
+- `--api-console-config`, path to the api-console-config.json file
+- `--yes` (`-y`), skip interactive confirmation and proceed with import
+
+- `--project-id`, to set the ID of the desired Project
+- `--auth-name`, the name of the miactl auth to use
+- `--endpoint`, to set the Console endpoint
+- `--certificate-authority`, to provide the path to a custom CA certificate
+- `--insecure-skip-tls-verify`, to disallow the check the validity of the certificate of the remote endpoint
+- `--context`, to specify a different context from the currently selected one
+- `--company-id`, to set the ID of the desired Company
+
 ## deploy
 
 The `deploy` command allows you to manage the deployment of your Projects.

examples/configuration-backoffice.json

@@ -0,0 +1,17 @@
+{
+  "projectId": "6821c8de556438a553188a10",
+  "tenantId": "33f78781-4f21-40eb-8a25-e3c6b09d3236",
+  "ref": "branches/demo-self-service",
+  "parentChangesId": "589b6904-742a-4f58-9f8c-4a0db5d418e7",
+  "configType": "backofficeConfigurations",
+  "config": {
+    "services": "...",
+    "version": "1.8.0"
+  },
+  "hash": "8e68e94dfb9af7f65e91aac2a08d5d49415924962e335ffa753c123063d89a9b",
+  "changesId": "3925c607-2cef-4b5d-934d-36a7102ef872",
+  "snapshotInfo": {
+    "message": "backup from {tenantId}-{projectId}-{ref}-{gg:mm:aaaa:hh:ss:ms} of Backoffice configuration document"
+  },
+  "__STATE__": "PUBLIC"
+}