[chore] increase resource limits for some load tests (open-telemetry#…

…34074)

**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
This PR increases some resource limits to make the load tests green for
now. Since they didn't run for 6 months, I assume some performance
degradation happened.
Example of a recent red load test run that just violated some resource
limits that will be fixed with this PR:
[link](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/9931396770)

**Link to tracking Issue:** [discussion on
slack](https://cloud-native.slack.com/archives/C07CCCMRXBK/p1721035998865689)

**Testing:** load tests only run on main branch

**Documentation:** NA

Signed-off-by: Moritz Wiesinger <[email protected]>

testbed/tests/metric_test.go

@@ -34,7 +34,7 @@ func TestMetric10kDPS(t *testing.T) {
 			receiver: datareceivers.NewCarbonDataReceiver(testutil.GetAvailablePort(t)),
 			resourceSpec: testbed.ResourceSpec{
 				ExpectedMaxCPU: 237,
-				ExpectedMaxRAM: 100,
+				ExpectedMaxRAM: 105,
 			},
 		},
 		{

testbed/tests/trace_test.go

@@ -206,7 +206,7 @@ func TestTraceNoBackend10kSPS(t *testing.T) {
 				t,
 				testbed.NewOTLPTraceDataSender(testbed.DefaultHost, testutil.GetAvailablePort(t)),
 				testbed.NewOTLPDataReceiver(testutil.GetAvailablePort(t)),
-				testbed.ResourceSpec{ExpectedMaxCPU: 80, ExpectedMaxRAM: testConf.ExpectedMaxRAM},
+				testbed.ResourceSpec{ExpectedMaxCPU: 90, ExpectedMaxRAM: testConf.ExpectedMaxRAM},
 				performanceResultsSummary,
 				testConf,
 			)