fix: resolve annotations with get_type_hints in attach_settings

[dusktreader]

Summary

• Fixes a NameError crash when attach_settings decorates a function whose annotations are stored as strings — either because the module uses from __future__ import annotations or because Python 3.14+ (PEP 649) stores annotations as strings by default
• attach_settings now calls typing.get_type_hints() to resolve annotations before comparing them against settings_model / SettingsManager, so string and evaluated annotations are handled identically
• Mutations to func.__annotations__ (the cloaking device injection that hides parameters from typer's help output) are preserved as-is

Root cause

The previous implementation read func.__annotations__ directly:

for key in func.__annotations__.keys():
    if func.__annotations__[key] is settings_model:

When annotations are strings (e.g. "CrolTrollSettings" instead of the class), the is comparison always fails silently — settings and manager parameters are never cloaked — and Python 3.14's annotation evaluation machinery can raise NameError: name 'Context' is not defined when it tries to resolve the string "Context" in the wrapper's scope.

Changes

• src/typerdrive/settings/attach.py: resolve via get_type_hints() before comparing
• tests/unit/settings/string_annotation_module.py: new helper module defined under from __future__ import annotations to replicate Python 3.14 string-annotation behaviour on all supported versions
• tests/unit/settings/test_attach.py: added TestStringAnnotations with two tests
• pyproject.toml: bumped to 0.9.2
• CHANGELOG.md: added entry for v0.9.2