fix: import command exits early on first failure when importing multiple artifacts

Nadie ha tomado este issue todavía.

Why we need this improvement:
When importing multiple comma-separated files, if one file fails,
the command immediately exits and remaining files are never imported.
Users have no visibility into which files succeeded and which failed.

How this will help:
All files should be attempted regardless of individual failures.
A summary at the end should show which files succeeded and which failed,
giving users complete feedback in one run.

Motivation:
This is a silent bug in CI/CD pipelines where partial imports can
cause hard-to-debug failures.

## Problem
When running:
microcks import "file1.yaml,file2.yaml,file3.yaml"

If file2.yaml fails, the command immediately calls os.Exit(1)
and file3.yaml is never imported. The user has no idea which
files were successfully imported and which were not.

## Proposed Fix
- Collect errors instead of exiting immediately
- Attempt all files regardless of individual failures
- Print a summary at the end showing pass/fail for each file
- Exit with code 1 only if any file failed

## Example output after fix
Importing 'file1.yaml'... success
Importing 'file2.yaml'... failed: connection refused
Importing 'file3.yaml'... success

Import completed: 2 succeeded, 1 failed

Comienza en el punto de entrada del comando de importación y localiza la ruta actual de os.Exit(1) que se usa cuando un artefacto falla. Ejecuta una importación de varios archivos con un archivo que falle para observar el comportamiento existente. Se considera terminado cuando se intenta procesar cada archivo, se informa de cada resultado, se muestra un resumen final de éxito o fallo y el comando termina con el código 1 cuando falla algún archivo.

Escrito por el modelo de indexación a partir del texto del issue.