Increase timeout for linux integration

[michalpristas]

What does this PR do?

This PR increases timeout for checking linux integration as it may sometimes take longer to recover.

Why is it important?

Debugging and reducing flakyness

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have run the Unit tests (make unit-test), and they are passing locally
• I have run the End-2-End tests for the suite I'm working on, and they are passing locally
• I have noticed new Go dependencies (run make notice in the proper directory)

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-09-22T15:58:10.527+0000

• Duration: 37 min 18 sec

• Commit: 8521706

Test stats 🧪

Test	Results
Failed	0
Passed	231
Skipped	0
Total	231

Steps errors

Expand to view the steps failures

Run functional tests for windows-2019:fleet:fleet_mode_agent && ~@nightly && ~debian && ~@skip:windo

• Took 15 min 2 sec . View more details here
• Description: cd e2e\_suites\fleet && go test -timeout 60m -v --godog.tags="fleet_mode_agent && ~@nightly && ~debian && ~@skip:windows && ~@skip:amd64"

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	231
Skipped	0
Total	231

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test

• jenkins run the tests

[mdelapenya]

I'd separate the time increase change from the services removal. Wdyt?

[michalpristas]

works for me, keeping increase

[adam-stokes]

Merging this, the failure is a result of elastic-agent on windows hitting that hard to find issue with a 400 status randomly