Add badges for project status and metrics

[soumeh01]

Changes

• Added various badges for license, maintainability, code coverage, security scorecard, CI builds, nightly builds, markdown linting, CodeQL analysis, and dependency review.
• Fine-tuned removal of badges before packing
• Removed redundant GPL license
• Updated version calculation algorithm during CI builds

Checklist

• 🤖 This change is covered by unit tests (if applicable).
• 🤹 Manual testing has been performed (if necessary).
• 🛡️ Security impacts have been considered (if relevant).
• 📖 Documentation updates are complete (if required).
• 🧠 Third-party dependencies and TPIP updated (if required).

[jkrech]

LGTM

[jkrech]

How do we make sure that these badges do not end up in the Extension View in VSCode.

[JonatanAntoni]

How do we make sure that these badges do not end up in the Extension View in VSCode.

We'd need to filter out the badges during npm package.

[soumeh01]

@jkrech @JonatanAntoni We already do that before packaging here
https://github.com/Open-CMSIS-Pack/vscode-cmsis-solution/blob/main/.github/workflows/ci.yml#L98-L101

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[jkrech]

LGTM