Update smart_date_module_implements_alter to include a #[LegacyModuleImplementsAlter] attribute

Thanks for taking this on, please add a note to remove the entire function once the minimum supported version of Drupal for the module is 11.2 or greater and link to the change record as well. https://www.drupal.org/node/3496788

Additionally, according to the instructions in the linked change record, step 1 is "Achieve the same functionality as your hook_module_implements_alter. Dynamic ordering is currently not supported."

The current state of the merge request seems to only address step #2
"Add the #[LegacyModuleImplementsAlter] to your implementation of hook_module_implements_alter. Once the minimum supported version of Drupal for the module is 11.2 or larger you may delete the entire function and attribute."

In my opinion we should change the scope of this issue to "Modernize Smart Date’s hooks to use Drupal 11’s attribute-based system" otherwise, the changes in the merge request are solely there to hide deprecation notices, which is probably not what we want.

If you agree please update the issue title to "Modernize Smart Date’s hooks to use Drupal 11’s attribute-based system"

See https://www.md-systems.ch/de/blog/2025-10-19/converting-legacy-hooks
See https://git.drupalcode.org/project/smart_date/-/blob/4.2.x/smart_date.to...
See https://git.drupalcode.org/project/smart_date/-/blob/4.2.x/smart_date.vi...

I believe this would involve adding the LegacyHook attribute to existing hooks, and creating new OOP Hook implementations for each existing hook.

Possible example

use Drupal\Core\Hook\Attribute\LegacyHook;
use Drupal\smart_date\Hook\SmartDateTokenHooks;
use Drupal\Core\Render\BubbleableMetadata;

/**
 * Shim for older Drupal versions (10.1–11.0).
 *
 * @phpstan-ignore-next-line
 */
#[LegacyHook]
function smart_date_tokens($type, $tokens, array $data, array $options, BubbleableMetadata $bubbleable_metadata) {
  return \Drupal::service(SmartDateTokenHooks::class)
    ->tokens($type, $tokens, $data, $options, $bubbleable_metadata);
}

Alternatively we can create a new issue to modernize and block this one with that one.