Add spring-config-guard to Tools > Testing

[rgiovann]

What

Adds spring-config-guard to the Tools > Testing section, in alphabetical order after SourceClear.

About the tool

A static analysis CLI that lints Spring Boot application.{yml,properties} files for security misconfigurations before deployment — Actuator endpoints exposed via management.endpoints.web.exposure.include=*, hardcoded credentials, insecure DB/broker TLS transport (useSSL=false, etc.), permissive CORS, and 12 other checks. Reports findings with a CI-gatable exit code, so it fails the build rather than getting discovered after the app is already running.

Apache 2.0, no dependency on Spring Boot itself (it statically parses the config files). Validated against real-world repositories, including Spring Boot's own source and a real Spring Cloud Config Server backing repository (spring-petclinic-microservices-config) via a dedicated Config Server mode.

Disclosure: I'm the author.

[rgiovann]

Small update since opening this PR — a few improvements to the project itself (not to this PR's diff):

• README: added an explicit target-audience statement and a paragraph differentiating spring-config-guard from generic static/YAML scanners like Checkov or a custom Semgrep rule — the real gap is that those don't model Spring's relaxed property binding or per-profile effective-config merge natively.
• Translated the remaining Portuguese-language comments in the codebase to English for consistency.
• Published the first GitHub Release (v1.0), jar included, so trying it out doesn't require cloning + building from source: https://github.com/rgiovann/spring-config-guard/releases/tag/v1.0

Happy to answer any questions about the tool, the rule set, or the validation runs in the README.