Mutating Spec.name during concretization invalidates hash values used in dictionary keys and causes non-local side effects for shared immutable specs (ref #51819). This leads to subtle bugs like these:

spec = Spec("+foo")
specs = {spec}
spec.name = "example"
assert spec in list(specs) # OK
assert spec in specs # AssertionError

and

empty_spec = Spec()  # shared, immutable singleton, used as "unconditional spec"
spec = empty_spec  # reference instead of copy, intentional, non-local
spec.name = "foo"  # as part of _condition_clauses
Spec("example").intersects(empty_spec)  # false; somewhere deep down the call chain from _condition_clauses

This commit removes the need for mutation by passing the package name as an explicit argument through the ASP generation logic. This was already the status quo for def _condition_clauses, the same pattern is simply propagated down the function call tree.

• Removed the named_spec context manager used for temporary renaming.
• Updated TransformFunction signature to (name, spec, facts).
• Added a name fallback argument to spec_clauses, spec_versions, and target_ranges.
• Updated _get_condition_id and _condition_clauses to use explicit names for caching and fact generation.
• Updated runtimes.py to use the name argument in spec_clauses instead of modifying the spec directly.