Complete elasticsearch tracking refactor

What does this MR do?

In !24895 (merged) we simplified the maintenance story for Elasticsearch record hooks. However, we missed two places where ElasticIndexWorker was enqueued directly instead of going through the new hooks.

When !24298 (merged) is merged, it will introduce significantly more conditionality into these hooks, so it's important that every part of GitLab uses them.

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Closes #38232 (closed)