Entity usage information can get stale when URLs are changed

Problem/Motivation

In 📌 Count usages after removal to ensure all usages have been removed Active we added a work around to recount and tell the user if there are usages left after removing entities. One of the causes of this is stale entity information.

Steps to reproduce

TBD

Proposed resolution

If there are outstanding queue items for entity_usage_recreate_tracking_data offer to process the queue and do not allow the link remover or entity usage updater to run. See 📌 Consider updating usage when path aliases change Active

Remaining tasks

User interface changes

API changes

Data model changes