Global Drupal.attachBehaviors() in init.js breaks other JS components.

Problem/Motivation

In js/init.js, when alerts are fetched and processed inside the initAlerts function, Drupal.attachBehaviors(); is called without a specific context element.

Because this call sits inside a forEach loop iterating over the active alerts, having multiple active alerts on the page causes Drupal.attachBehaviors() to fire globally on the entire document multiple times in rapid succession (once for each active alert).

We ran into this issue when it completely broke our custom tabs and accordions. Because the script re-runs across the entire page for every single active alert, it stacked multiple click listeners onto our buttons, causing them to glitch out. While we can update our own theme to guard against this, passing the context is a great best practice to ensure the module works smoothly across all types of projects and themes without causing accidental conflicts.

Steps to reproduce

1. Have a site with custom JavaScript behaviors attached to DOM elements (like tabs or accordions).
2. Create and activate more than one Sitewide Alert so that the alerts.forEach loop runs multiple times.
3. Load a page displaying these alerts.
4. Observe that Drupal.attachBehaviors() is fired globally multiple times, causing unexpected behavior in other JavaScript components on the page.

Proposed resolution

Scope the behavior attachment specifically to the newly rendered alert element.

Change:
Drupal.attachBehaviors();

To:
Drupal.attachBehaviors(renderableAlertElement);

This ensures that behaviors are only attached to the markup injected by the module, preventing it from unnecessarily rescanning the entire page and interfering with other components.