Introduce linters to protect and maintain code quality.

[tyzerrr]

SSIA
I prefer to introduce this, built by Netflix.

[tyzerrr]

@draeger Could I take this issue?
I will make CI/CD pipeline with Github Actions.

Goal is below.
[Goal of this issue]

1. Build the way to check whether all tests and all lint check pass or not.
2. Migrate from maven to gradle, this is related Migrate from Maven to Gradle #77.

If I can understand how to migrate from Gradle, I'll also take this issue.
If you think this is fine, could you assign me, and also could you make me Maintainer of this project?
I think this is one of the greatest contribution.

[baranwalayush]

@tyzerrr @draeger I've been reading about this recently and I think maven already supports almost everything associated with "linting". Like, we can use spotless for formatting, checkstyle for style checks and others. We can integrate it with the CI/CD pipeline too. Let me know what do you think. I'd be happy to dive deeper in this, if required.

[draeger]

Dear @baranwalayush, thank you for looking into this.

I agree that Maven already provides a good ecosystem for code quality checks, so I do not see an immediate need to switch build systems for this purpose.

Before we proceed, it would be helpful to have a concrete proposal. For example:

• Which tools would you recommend introducing (e.g., Spotless, Checkstyle, SpotBugs, PMD)?
• Which rulesets would be enabled initially?
• How many violations do these tools currently report on SBSCL?
• Would you suggest fixing all existing violations, or only enforcing the rules for newly introduced code?
• How would the checks be integrated into the CI pipeline?

If you are interested in working on this, I would be happy to review a short proposal or proof-of-concept pull request.