Synchronize GH Actions with KphpStorm repo

[vldF]

1. Add the release workflow — the same as KphpStorm's one
2. Introduce Qodana support — the same as KphpStorm's one
3. Fix some critical code problems based on Qodana analysis. There are a plenty of code issues, however, they can't be fixed as easy as these
4. Update project dictionaries to reduce false-positive Qodana issues findings
5. Add project inspections profile — the same as KphpStorm's one

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.1.1
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[Hidanio]

Why? Something like global singleton?

[vldF]

We always need to pass Service.Level.PROJECT as the only argument of @Service annotation because in another case the service will be application-wide. Application services can't get project with their constructors

private constructor is the most convenient way to deny direct instance creation. This shows that developer must use some other way (e.g. getInstance()) to obtain it