Fix test targets in jetty other than 'test'

[cataphract]

Two problems:

• The addTestSuiteForDir calls were for adding only targets that don't run the *ForkedTests.
• When adding ForkedTest targets, the gradle "configurations"' name are based upon the sourceSet name. DefaultJvmTestSuite uses as the sourceSet name the name of the task. Consequently, if we add a target called latestDepForkedTest, the created configurations are named latestDepForkedTestImplementation and so on, whereas the current dependencies {} blocks are only adding dependencies on latestDepTestImplementation. Fix this by making the ForkedTest configurations extend from the non-Forked ones (e.g. latestDepForkedTestImplementation extends from latestDepTestImplementation; latestDepTestImplementation is created if it doesn't exist).

[pr-commenter]

Benchmarks

Parameters

	Baseline	Candidate
commit	1.14.0-SNAPSHOT~41ae2f7dec	1.14.0-SNAPSHOT~d9d8c0bce0
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	same
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	same
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