Function CRD applied endpoint/status are single-valued fields, but Functions can be applied to multiple databases

When `Function` instances are created with a `database: '*'` target, Ingestor applies the function to all of the databases it knows about. However, the `AppliedEndpoint` and `Status` fields are singular values so the field just gets a single value. This prevents us from seeing the application status for all of the endpoints and may cause Ingestor to try re-applying to databases because it only sees the status for a different DB.

Start by locating the Function CRD definition and the Ingestor reconciliation and status-update paths for the database: '*' target. Trace how AppliedEndpoint and Status are written when multiple databases are affected. Done means status exposes every applied endpoint and Ingestor does not re-apply a function because it sees only another database's status.

Written by the indexing model from the issue text.