Static Code Analysis and Quality Gates

@Col-E, how do you feel about modifying the GitHub workflows to include static code analysis?

For background, I added analysis steps for [SonarQube Cloud](https://sonarcloud.io), [Qodana](https://qodana.cloud), and [CodeQL](https://codeql.github.com/) in the persistence fork, and they've been very helpful in pointing out potential bugs, potential NPEs, gaps in test coverage, etc. I've already fixed the issues discovered in the persistence modules, but there are still issues in the `core` module. Analysis in the fork is configured to ignore the `core` and `demos/basic` modules, so porting the configuration **shouldn't** break anything. Those modules can be included as findings in them are resolved. I'd be happy to open issues for them and implement most as separate PRs.

Adopting the changes would require creating a [SonarQube Cloud](https://sonarcloud.io) account and generating an access token. [Codecov](https://codecov.io) and [Qodana Cloud](https://qodana.cloud) accounts would be needed as well, each with its own token. So we'd likely want to coordinate closely to avoid downtime. I don't want to "move any cheese," but I'm willing to port them over if it's something you actually want. Let me know if you're interested.

Start by reviewing the repository's GitHub workflows and the static-analysis configuration from the persistence fork, noting how the core and demos/basic modules are excluded. Check the required SonarQube Cloud, Qodana Cloud, Codecov, and CodeQL setup and credentials; done means the analysis workflows and quality gates run reliably without downtime.

Written by the indexing model from the issue text.