task_local context over context objects

- interner impls logically separate from API in orchid-base (default host interner still in base for testing)
- error reporting, logging, and a variety of other features passed down via context in extension, not yet in host to maintain library-ish profile, should consider options
- no global spawn mechanic, the host has a spawn function but extensions only get a stash for enqueuing async work in sync callbacks which is then explicitly, manually, and with strict order popped and awaited
- still deadlocks nondeterministically for some ungodly reason

orchid-std/src/std/string/to_string.rs

@@ -3,7 +3,6 @@ use orchid_api_traits::Request;
 use orchid_base::name::Sym;
 use orchid_extension::atom::{AtomMethod, Atomic, MethodSetBuilder, Supports};
 use orchid_extension::atom_thin::{ThinAtom, ThinVariant};
-use orchid_extension::context::i;
 
 use crate::std::protocol::types::{GetImplMethod, GetTagIdMethod};
 
@@ -19,7 +18,7 @@ impl Atomic for AsStrTag {
 impl ThinAtom for AsStrTag {}
 impl Supports<GetTagIdMethod> for AsStrTag {
 	async fn handle(&self, _: GetTagIdMethod) -> <GetTagIdMethod as Request>::Response {
-		Sym::parse("std::string::to_string", &i()).await.unwrap().to_api()
+		Sym::parse("std::string::to_string").await.unwrap().to_api()
 	}
 }
 impl Supports<GetImplMethod> for AsStrTag {