Replace console.error with structured logger in recordScraperRun

Switch error logging from console.error to the injected logger.error
pattern for consistency with the rest of the scraper service layer.
Update tests to verify logger.error is called instead of console.error.

services/scraperService.js

@@ -626,9 +626,10 @@ async function updateDailySummary(db, summaryData, logger) {
  *
  * @param {Db} db - MongoDB database instance
  * @param {Object} runData - Run data to record (jobId, trigger, status, duration, etc.)
+ * @param {Object} logger - Logger instance
  * @returns {Promise<Object|null>} Insert result, or null on failure
  */
-async function recordScraperRun(db, runData) {
+async function recordScraperRun(db, runData, logger) {
   const collection = db.collection(config.COLLECTIONS.SCRAPER_RUNS);
 
   try {
@@ -641,7 +642,7 @@ async function recordScraperRun(db, runData) {
 
   } catch (error) {
     // Log but don't throw - recording history should not break scraper
-    console.error('Failed to record scraper run:', error.message);
+    logger.error('Failed to record scraper run', { errorMessage: error.message });
     return null;
   }
 }