Capture asset deletion in discovery

[bsushmith]

Is your feature request related to a problem? Please describe.
In the current data discovery system, whenever an asset(eg: table/job) gets deleted, the deletion information is not passed down to the compass from the meteor., and compass will show these deleted assets.

Meteor should capture these deletes and pass down the information to compass service so that it can process them accordingly.

Options:

1. capture asset delete at source by reading logs or through hooks
2. do a timely reconciliation between source and compass asset lists.

[vnmxcmnjane-hub]

• - #<img width="2700" height="2700" alt="Image" src="https://github.com/user-attachments/assets/e00ddac3-1da0-4d58-8b49-f8d2b9f7ed33" />

• [ ###

]:♡※※※※※※※※7

• feed ^.,anomaly flag of a static RTTY-like response

• <img width="2400" height="2400" alt="Image" src="https://github.com/user-attachments/assets/7c6d95a9-8d9c-4a83-b0da-165d0e19c5f3" />


[ravisuhag]

Closing as part of roadmap cleanup. Superseded by #507 (Add change detection and watermark tracking to extractors), which covers asset deletion detection as part of incremental extraction with change type metadata (created, updated, deleted).

See: docs/docs/roadmap.md