Don't use strictly for testng dependency

[bantonsson]

What Does This Do

Changes back a strictly directive to a force clause

Motivation

When running dependencies on the testng project gradle reports a FAILURE and IntelliJ IDEA will report an ERROR when importing the project.

Additional Notes

[pr-commenter]

Benchmarks

Parameters

	Baseline	Candidate
commit	1.14.0-SNAPSHOT~5e079a8865	1.14.0-SNAPSHOT~c4528f0de0
config	baseline	candidate

See matching parameters

	Baseline	Candidate
module	Agent	Agent
parent	None	None

Summary

Found 0 performance improvements and 0 performance regressions! Performance is the same for 22 cases.

See unchanged results

scenario	Δ mean execution_time
scenario:Startup-base-Agent	same
scenario:Startup-base-Agent.start	same
scenario:Startup-base-BytebuddyAgent	unsure [-4.241ms; -0.126ms] or [-0.720%; -0.021%]
scenario:Startup-base-GlobalTracer	same
scenario:Startup-base-AppSec	same
scenario:Startup-base-Remote Config	same
scenario:Startup-base-Telemetry	same
scenario:Startup-iast-Agent	same
scenario:Startup-iast-Agent.start	same
scenario:Startup-iast-BytebuddyAgent	same
scenario:Startup-iast-GlobalTracer	same
scenario:Startup-iast-AppSec	same
scenario:Startup-iast-IAST	unsure [+0.009ms; +0.488ms] or [+0.077%; +4.347%]
scenario:Startup-iast-Remote Config	same
scenario:Startup-iast-Telemetry	same
scenario:Startup-waf-Agent	same
scenario:Startup-waf-Agent.start	same
scenario:Startup-waf-BytebuddyAgent	same
scenario:Startup-waf-GlobalTracer	same
scenario:Startup-waf-AppSec	same
scenario:Startup-waf-Remote Config	same
scenario:Startup-waf-Telemetry	same