Wrong Microcks CLI executable configured in spring-boot-order-service

[abkacimi]

Describe the bug

The docker-compose file for spring-boot-order-service is referencing an incorrect Microcks CLI executable and option.

api-lifecycle/shift-left-demo/spring-boot-order-service/microcks-docker-compose.yml

Lines 10 to 17 in 5c67921

	entrypoint:
	- microcks-cli
	- import
	- '/resources/order-service-openapi.yaml:true,/third-parties/apipastries-openapi.yaml:true,/third-parties/apipastries-postman-collection.json:false'
	- --microcksURL=http://microcks:8080/api
	- --insecure
	- --keycloakClientId=foo
	- --keycloakClientSecret=bar

the executable is defined as microcks-cli, but the correct executable name is microcks.
Additionally, the CLI option --insecure is not valid and must be replaced with --insecure-tls.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Microcks version or git rev

No response

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

No response

Additional information

No response

[github-actions]

👋 @amkac

Welcome to the Microcks community! 💖

Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"

Hope you have a great time there!

🌟 ~~~~~~~~~ 🌟

📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!

🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.