Re-run Drupal cron (scheduled) tasks on our environments

[jamestranovich-noaa]

Description

Our general structure for Drupal-on-cloud.gov comes from this repository which is not updated anymore. Specifically we have a cronish.sh script borrowed from that repository that is supposed to be run as a cloud.gov task but it has been disabled (for all environments) since late 2023.

Drupal's cron in this case is a scheduler that handles upkeep (optimizing the database, clearing the cache, etc) and invokes per-module cron calls (so that modules themselves can do periodic upkeep as well). For an overview, see this Drupal cron documentation.

There's a few problems here:

• If automated tasks are pending, and cron tasks have not been run for a while (about 3 hours), cron will slow down the Drupal page because it runs its tasks as a prelude to a page request.
• We shouldn't be running cron in maintenance mode or when updating Drupal or when doing a release. Doing so is undefined behavior (and likely will outright break Drupal.) So, we want to check drush maint:status beforehand in the script.
• We have no way of currently tracking what actions cron takes, exactly. Cron logging should happen as per NR documentation but it's not clear if it actually does.

A list of cron tasks that are currently run (not all of these do anything every time):

• update_cron()
• system_cron()
• scheduler_cron()
• node_cron()
• locale_cron()
• layout_builder_cron()
• file_cron()
• field_cron()

I propose that we re-enable cronish for all environments and/or enable NR or equivalent logging when we do so.

Acceptance criteria

• [ ] We re-enable cron and monitor it appropriately

[colinmurphy01]

Can you hit me with a priority assessment?

[jamestranovich-noaa]

I'll defer to @eric-gade but I think this is low. That is, this feature would be nice to have, but by no means essential. That might change, however, if we have an uptick in beta.weather.gov usage.