docs(shared): drop __future__ module references from project_resolver docstrings (#68)

The __future__ domain object (LogStream, Experiment, ...) references were
stale placeholders; simplify the docstrings to describe the resolver in
terms of the modules that exist today.

Author: fercor-cisco

src/splunk_ao/shared/project_resolver.py

@@ -1,9 +1,9 @@
 """Shared helper for resolving a project from explicit params or env fallbacks.
 
-Lives alongside :func:`splunk_ao.shared.exceptions._project_not_found_error` so the
-two helpers — "how to find a project" and "what error to raise when you can't" —
-sit in one place and can be reused by every ``__future__`` domain object
-(LogStream, Experiment, …) instead of being duplicated per-class.
+This lives alongside :func:`splunk_ao.shared.exceptions._project_not_found_error`
+so the two concerns — how to find a project, and what error to raise when one
+can't be found — stay together in one place and can be reused across modules
+instead of being duplicated in each one.
 """
 
 from __future__ import annotations

tests/shared/test_project_resolver.py

@@ -1,9 +1,8 @@
 """Unit tests for ``splunk_ao.shared.project_resolver._resolve_project``.
 
-The resolver is the single canonical entry point used by every ``__future__``
-domain object (LogStream, Experiment, …) to turn explicit kwargs / env vars
-into a concrete project. These tests pin its contract so future callers
-behave consistently.
+This resolver is the single canonical entry point every module should use to
+turn explicit kwargs or env vars into a concrete project. These tests pin
+down its contract so future callers behave consistently.
 """
 
 from unittest.mock import MagicMock, patch