enhance(cli): add colored CLI version message

[arshinsikka]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• [✅] Feature addition or enhancement
• Code maintenance
• DevOps
• [✅] Improve developer experience
• Others, please explain:

Overview of changes:
This pull request enhances the MarkBind CLI output by adding color to the version header message using the chalk library. Specifically, it updates the printHeader() function to display a green checkmark and version string for improved visibility and user experience.

Before:

v5.0.2

After:

✔ MarkBind CLI v5.0.2 (in green)

Anything you'd like to highlight/discuss:

No major concerns. This change is minimal, cosmetic, and backwards-compatible. Open to suggestions on color choices or formatting style.

Testing instructions:

Run the CLI using:
npx markbind

You should see the new green checkmark version string in the terminal.

Proposed commit message: (wrap lines at 72 characters)

enhance(cli): add colored CLI version message using chalk

Adds a green checkmark and CLI version text using chalk in the
printHeader function of the MarkBind CLI.

This improves the visibility and visual feedback of the version
display when users run the CLI.

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• [✅ ] Linked all related issues
• [✅ ] No unrelated changes

---

Reviewer checklist:

Indicate the SEMVER impact of the PR:

• Major (when you make incompatible API changes)
• Minor (when you add functionality in a backward compatible manner)
• [✅] Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

• To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

• what was the old feature that was made obsolete
• any replacement feature (if any), and
• how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

[damithc]

@arshinsikka As this is an experimental change, you can create the PR within your own fork, and also include screenshots (before and after) or a screen recording to show how the feature works.
Closing this PR ...