feat(unit-tests): increase code coverage

[dmitrii-kiselev]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows Conventional Commits
• Tests for the changes have been added (for bug fixes/features)
• Docs have been added/updated (for bug fixes/features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Refactoring (no functional changes, no API changes)
• Other... Please describe:

What is the current behavior?

• No pull request template
• No unit tests for the DbCommandInterceptorProcessor class
• No unit tests for the SecondLevelCacheInterceptor class
• Unit tests are not run when creating a pull request or merging into the master

What is the new behavior?

• Pull request template (this will ensure that pull requests are filled in detail when new people create them)
• The DbCommandInterceptorProcessor class is covered by 100%
• The SecondLevelCacheInterceptor class is covered by 98%
• Unit tests are run when creating a pull request or merging into the master (this will give confidence that the changes do not break the existing logic)

Overall code coverage increased from 19% to 35%:

Does this PR introduce a breaking change?

• Yes
• No

Other information

This work improves the overall quality of the project.

Best Regards,
Dmitrii Kiselev

[what-the-diff]

PR Summary

• Introduction of a Pull Request Template
  A template for new pull requests has been added. This model includes a checklist that guides the user during the submission process, helping assign the type of pull request and define the existing and new behavior, as well as clarifications on potential large scale changes. This simplification is intended to increase consistency and clarity across all submitted requests.

• Enhancement of GitHub Actions Workflow
  In the workflow file responsible for building the repository, a new task has been included that enables automatic unit testing for the software library named EFCoreSecondLevelCacheInterceptor. This action not only runs the tests against the particular software section but also creates comprehensive log reports about the tests’ outcomes. This added system increases code reliability and visibility for developers inspecting the output.