Add contribution guidance (CONTRIBUTING.md)

[dgarske]

Description

Adds a CONTRIBUTING.md to the repository root. None of the wolfSSL repositories had one, so our contributor agreement requirement was only discovered after someone had already done the work. See wolfSSL/wolfssh#1146, where an outside contributor withdrew a PR over it and asked us to document the requirement up front.

The same repo-agnostic file is being added to wolfSSL, wolfSSH, wolfMQTT, wolfTPM, wolfBoot, wolfPKCS11, wolfHSM, wolfProvider, wolfSentry and wolfCLU. It covers how to contribute, the contributor agreement and how to request one, our CI (GitHub Actions is public, Jenkins failures get pasted in by a maintainer), coding expectations, and where to report security issues. Please read the file itself rather than a summary here.

Testing

Documentation only - no code changes.

[Copilot]

Pull request overview

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Adds a repository-root CONTRIBUTING.md to make wolfSSL Inc.’s contribution process (especially the required contributor agreement) explicit up front, addressing prior contributor confusion.

Changes:

• Introduces a standardized contribution guide applicable across wolfSSL Inc. repositories
• Documents contributor agreement requirement and alternatives when it can’t be signed
• Describes CI visibility (GitHub Actions vs internal Jenkins) and security reporting process

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.