feat: intergrate logging function

[hanzili]

Related Issue

When executing installation script, user can easily miss the log message and continue using keploy with a fail initlization (that's what happened to me T^T

Closes: #1701

Describe the changes you've made

• Introduced log_message for standardized and color-coded logging.
• Enhanced error handling to pause script execution and ensure user have acknowledged the errors.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Please let us know if any test cases are added

NA

Describe if there is any unusual behaviour of your code(Write NA if there isn't)

NA

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

Screenshots (if any)

Now, when there is an error level logging, the execution will be paused until user acknowledge the message.

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[github-actions]

Thank you and congratulations 🎉 for opening your very first pull request in keploy

[hanzili]

I have read the CLA Document and I hereby sign the CLA

[shivamsouravjha]

@hanzili it would be better if Keploy logs that docker daemon isn't running, reason being if someone has keploy installed, restarted laptop or stopped docker manually, once they try to run keploy they would face similar issue.

So it would be better approach to rather log in keploy

[hanzili]

@hanzili it would be better if Keploy logs that docker daemon isn't running, reason being if someone has keploy installed, restarted laptop or stopped docker manually, once they try to run keploy they would face similar issue.

So it would be better approach to rather log in keploy

Sorry for getting back so late! Do you mean checking is docker is running when keploy starts? Could you explain more about the issue when someone restarted laptop or stopped docker manually as you mentioned? It sounds like a different issue than the one I encountered. My issue is that the keploy installation script does not initialize everything needed to run keploy (like creating keploy-network) and I did not realize that when using keploy.