x-pack/filebeat/input/azureblobstorage: reduce tested maximum worker …

…load (#36358) (#36360)

The 3000 workers test case is unreasonably high; there is no real
justification for this many workers operating on a network-bound system
and there is some reason to believe that on some systems this may be
causing system i/o resource depletion and failure of unrelated tests.

(cherry picked from commit 5258cb2)

Co-authored-by: Dan Kortschak <[email protected]>

x-pack/filebeat/input/azureblobstorage/input_test.go

@@ -399,7 +399,7 @@ func Test_StorageClient(t *testing.T) {
 }
 
 func Test_Concurrency(t *testing.T) {
-	for _, workers := range []int{100, 1000, 2000, 3000} {
+	for _, workers := range []int{100, 1000, 2000} {
 		t.Run(fmt.Sprintf("TestConcurrency_%d_Workers", workers), func(t *testing.T) {
 			const expectedLen = mock.TotalRandomDataSets
 			serv := httptest.NewServer(mock.AzureConcurrencyServer())