Fix LinkCrawlWorker error when encountering empty OEmbed response

[ClearlyClaire]

Fixes #28233

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (f3864db) 83.47% compared to head (303d8e8) 83.47%.
Report is 2 commits behind head on main.

Files	Patch %	Lines
app/services/fetch_oembed_service.rb	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #28268   +/-   ##
=======================================
  Coverage   83.47%   83.47%           
=======================================
  Files        1038     1038           
  Lines       28230    28230           
  Branches     4554     4554           
=======================================
  Hits        23565    23565           
  Misses       3536     3536           
  Partials     1129     1129           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stevek101]

Since installing 4.2.4, the IndexingScheduler is running nonstop (4-7 Scheduler::IndexingScheduler jobs running). This is maxxing the CPU. Could this be related to the LinkCrawlWorker changes?

[ClearlyClaire]

No, that does not seem related at all. Can you open an issue for this, with information on your Elasticsearch deployment, whether you updated from 4.2.3 or from an older release, what size your instance is and whether you have had a recent increase in traffic?