DT-921: Add Spotless to build process.

[rushtong]

Addresses

Addresses https://broadworkbench.atlassian.net/browse/DT-921 only for Consent-Ontology

Summary

Adds spotless to the build process. PRs will potentially fail the maven action if there are any formatting problems.

This PR is limited to these things:

1. Adding the spotless plugin
2. Update the checkout for specific actions so they fetch origin/develop. Necessary to apply the ratchetFrom configuration option for spotless.
3. Applying the results of mvn spotless:apply
4. Ignore semgrep warning from updating StorageFactory

There are some outstanding cleanup problems that we can address in a future PR/ticket, for example, there are some unused classes touched in this PR like UseRestrictionKeys and ValidationResponse.

---

Have you read CONTRIBUTING.md lately? If not, do that first.

• Label PR with a Jira ticket number and include a link to the ticket
• Label PR with a security risk modifier [no, low, medium, high]
• PR describes scope of changes
• Get a minimum of one thumbs worth of review, preferably two if enough team members are available
• Get PO sign-off for all non-trivial UI or workflow changes
• Verify all tests go green
• Test this change deployed correctly and works on dev environment after deployment

[rjohanek]

what does this do?

[fboulnois]

This downloads the current version of the repository instead of the entire repository history.

[rushtong]

This is what I described in step 2 - it fetches the full history of the repo so that the local checkout has access to the origin/develop branch. See https://github.com/actions/checkout for docs. Without this, spotless isn't able to apply the rachetFrom configuration.

[rjohanek]

spotless changes look good, thanks!

[fboulnois]

How does this interact with our checked-in codeStyles?

[rushtong]

How does this interact with our checked-in codeStyles?

It applies the googleJavaFormat style which is what we currently use.

[rushtong]

Going to close this for the time being. We need to better clarify where this should sit in the local build/dev/deploy cycle and how to deal with potential conflicts with .idea/codeStyles