Loose foreign key worker should override feature category from table

The loose foreign key worker processes data for specific tables, but when there are issues it raises those issues in the DBF channel, making us triage the worker to figure out what tables are impacted and why. Instead, the worker should alert the table owners. The worker itself already knows what table it's processing, and we know which teams own tables. We should update feature category for the worker like we do for batched background migrations.

Deliverables

• LFK Worker overrides feature category from db dictionary