Added loggers for Fleet enrollment call failures

[Rohit-code14]

• Enhancement

What does this PR do?

Added logger to print the status and code when enrollment call to fleet failed.

Why is it important?

As mentioned in the issue(#6287), It will be difficult to debug enrollment failures in such cases. Therefore adding the actual status code and error in logs will be helpful for debugging.

Checklist

• I have read and understood the pull request guidelines of this project.
• 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

No disruptive user impact

Related issues

• Closes Remote server failed to handle the request, will retry in a moment needs to be better handled #6287

[mergify]

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

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

[pkoutsovasilis]

buildkite test this

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[pkoutsovasilis]

buildkite test this

[pkoutsovasilis]

buildkite test this

[pkoutsovasilis]

buildkite test this

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube