## Summary

Add links to relevant areas for agentless connector:
- link integration owning this connector
- if policy related to this connector exist:
   -  add link to view policy
   - otherwise display `No policy found`
- if agent related to this policy exists
  - display agent status (e.g. is it offline, or any other state)
  - link to fleet agent host overview
- create discover app link to show logs related to agent/connector for
the past 6 hrs (select relevant columns :) )
  - otherwise, handle this

Changed isWaitingOnAgentlessDeployment to just check whether `last_seen`
(connector heartbeat field) was populated, this is to address this
reported [issue](https://github.com/elastic/search-team/issues/9165).

### Happy path

https://github.com/user-attachments/assets/76db0b66-dda3-43a7-a74b-79348c7e7989

### Handling edge cases

#### No agent / inactive agent

https://github.com/user-attachments/assets/eae9b8da-de24-4d77-bc9e-b7cfad75b426

similarly we handle edge cases with policy not existing yet

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ x [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: José Luis González <joseluisgj@gmail.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 0edba39)