feat: Add import-dir command for bulk importing API specifications

[Caesarsage]

• Introduced a new command import-dir to allow users to import multiple API specification files from a specified directory.
• Implemented functionality to scan for supported file types (.yaml, .yml, .json, .xml) and handle recursive imports.
• Added unit tests to ensure the reliability of the import process.
• Updated documentation to include usage examples and details about the new command.

This feature enhances the CLI's capabilities for managing API specifications efficiently.

Related issue(s)

Fixes #171

Addresses: #97 (Support for directory import)

[Harsh4902]

@Caesarsage Thank you so much for this PR. It's actually a very good implementation for import-dir command. I have some concerns:

• Maybe we can use existing API sspecifications which are already present in /sample/ directory.
• We are thinking to move all import related commands as sub-command like import url, import dir, so maybe we can integrate this after the migration. It will basically reduce the overhead after the new implementation.

[Caesarsage]

Kindly review @lbroudoux @hash

@Caesarsage Thank you so much for this PR. It's actually a very good implementation for import-dir command. I have some concerns:

• Maybe we can use existing API sspecifications which are already present in /sample/ directory.
• We are thinking to move all import related commands as sub-command like import url, import dir, so maybe we can integrate this after the migration. It will basically reduce the overhead after the new implementation.

Thank you for the feedback and for reviewing the PR! @Harsh4902
I can update the PR to use only the existing API specifications in the /samples/ directory and remove any extra sample files I added for demonstration/testing.

for the command restructure, I agree it would be more efficient to integrate the import-dir functionality after the import commands are refactored into sub-commands.

Please let me know when the migration is complete, and I’ll be happy to rebase and adapt this PR to fit the new structure.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[lbroudoux]

Thanks for your patience @Caesarsage! This is great work and I'd like to introduce a first version of it in the next 1.0.1 release. I'm going to merge this one in the microcks:1.x branch and then merge it back (and resolve potentiel conflicts in master).

Thanks a lot for this contribution!