fix getProviderFromDomain function, move from integration test

[aspacca]

Bug

What does this PR do?

fix logic to discover provider from endpoint in getProviderFromDomain

Why is it important?

#28234 introduced the possibility to use not AWS S3 bucket as input for filebeat.
A function was added to discover the provider when using custom endpoints
The logic was broken since the test were using the wrong input for the function.
We didn't spot during CR of the PR because the test for the function was added to integration test file, that has a build constraint that skip it from running during PR

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label. Could you fix it @aspacca? 🙏
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 7./d branch. /d is the digit

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

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-getProviderFromDomain-filebeat-aws-s3-input upstream/fix-getProviderFromDomain-filebeat-aws-s3-input
git merge upstream/master
git push upstream fix-getProviderFromDomain-filebeat-aws-s3-input

[elasticmachine]

Pinging @elastic/integrations (Team:Platforms)

[elasticmachine]

💚 Build Succeeded

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

Expand to view the summary

Build stats

• Duration: 96 min 1 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[endorama]

I just added a comment to clarify the intention of the change but LGTM. Is my understanding that integration tests are not run, or I did not understand why they did not catch the bug 🤔

[aspacca]

Is my understanding that integration tests are not run

the test was added in the integration test file that has //go:build integration && aws and (as far as I got it) it's run only weekly or similar. so it didn't run in the PR and we didn't catch the bug