test: use a lower unenroll timeout in TestActionUnenrollHandler

[kruskall]

What does this PR do?

auto unenroll with no running components is timing out after 15s due to hardcoded unenrollTimeout.
There is no need to use a huge timeout in test. Pass the timeout as a method arg and use a lower timeout.

Test time went from 15s to 0.1s

Why is it important?

slow tests are not good

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 added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

go test ./internal/pkg/agent/application/actions/handlers/. -run=TestActionUnenrollHandler/auto_unenroll_with_no_running_components -v

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @kruskall? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
50.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube