[tests-only] use jest.mocked instead of mocked from ts-jest/utils

[individual-it]

Description

the mocked util function is now deprecated and has been moved to Jest repository, see https://github.com/facebook/jest/pull

the log output is probably there since bumping jest to 27.x 7fa3b71

alternative is to disable the warning with process.env.DISABLE_MOCKED_WARNING=true but I don't see why that should be good
@pascalwengerter (you have bumped jest) @fschade (you have written the tests) opinions?

Related Issue

• part of Lots of warnings & errors when running unit tests #6337

Motivation and Context

get rid of this log output

 `mocked` util function is now deprecated and has been moved to Jest repository, see https://github.com/facebook/jest/pull/12089. In `ts-jest` v28.0.0, `mocked` function will be completely removed. Users are encouraged to use to Jest v27.4.0 or above to have `mocked` function available from `jest-mock`. One can disable this warning by setting environment variable process.env.DISABLE_MOCKED_WARNING=true

How Has This Been Tested?

• running unit tests locally
• 🤖

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

Open tasks:

• ...

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[pascalwengerter]

LGTM, thanks for taking care!