[Fleet]: Incorrect error message is displayed at the top of the policy editor while adding AWS integration when no Fleet Server exists.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.14.0-SNAPSHOT
BUILD: 73413
COMMIT: cba0e7f3f18ab7fd48ee30b0385a599d211eac7d

Host OS: All

Preconditions:

1. 8.14.0-SNAPSHOT Kibana cloud environment should be available.

Steps to reproduce:

1. Navigate to Fleet>Agents tab and observe no hosted fleet server is available.
2. Navigate to Integrations and add AWS integration.
3. Observe error message:
   This integration contains policy secrets(opens in a new tab or window), but you have a Fleet Server running on a version earlier than 8.10.0. Please upgrade your Fleet Server to enable policy secrets for all integrations.

Expected Result:
Correct error message should be displayed under policy editor while adding AWS integration when no Fleet Server exists.
This integration contains policy secrets(opens in a new tab or window), but Fleet Server is not available. Please install Fleet Server to enable policy secrets for all integrations.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-04-17.11-31-46.mp4

Feature:
#178045

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary review for this ticket is Done

[kpollich]

Thanks for the report. I think providing a granular message like this is doable, but we should consider this pretty low priority for now.

[kpollich]

For context: we'd need to do an additional check for Fleet Servers first before showing the callout, which I think we could do it's just a bit tedious.