[Request] Target Lineage view should use working database, not audit records, when available

### Describe the feature

https://github.com/cryostatio/cryostat-web/pull/2065#issue-3867343094

> This currently always calls into the backend's new audit endpoint to determine the target's lineage based on historical audit records, but for currently available/discovered targets this information is also present in the regular discovery tree, which should be a more performant query when it's available.

### Anything other information?

_No response_

Start by reading the linked pull request and tracing the Target Lineage view's current use of the backend audit endpoint. Compare that path with the regular discovery tree, then verify that currently available targets use the working database when present while unavailable targets retain the audit-record behavior.

Written by the indexing model from the issue text.