Fix: Pass preferences parameter to generateAlertEmailContent in air-quality-alerts-job

[coderabbitai]

Issue Description

The generateAlertEmailContent function in src/auth-service/bin/jobs/air-quality-alerts-job.js expects three parameters: spikes, userName, and preferences. However, in the current implementation, only two arguments are being passed when calling this function, which could lead to runtime errors when the function tries to access the preferences parameter.

Current Implementation

const emailPromises = batch.map(async ({ user, spikes }) => {
  const content = generateAlertEmailContent(spikes, user.firstName);

Expected Implementation

const emailPromises = batch.map(async ({ user, spikes, preferences }) => {
  const content = generateAlertEmailContent(spikes, user.firstName, preferences);

Impact

• Potential runtime errors when accessing preferences data
• Incorrect threshold values in email alerts
• Missing site-specific preferences in the generated email content

References

• Pull Request: initial set up of the notifications preferences use case #4204
• Discussion: initial set up of the notifications preferences use case #4204 (comment)