[DI] Convert two more order-independent collections to autodiscover

[TomasVotruba]

Follow-up to #8370. Converts two more collections from registerTagged() to autodiscover().

Both were previously held back as "order-sensitive", but verification shows their consumers match mutually exclusively — no input can match two entries — so filesystem registration order is irrelevant:

Collection	Consumer	Why order-independent
NodeNameResolverInterface	is_a($node, $resolver->getNode())	10 distinct PhpParser nodes, no inheritance overlap among the targets
PhpDocTypeMapperInterface	is_a($typeNode, $mapper->getNodeType())	4 siblings that all implements TypeNode, none extends another

The remaining registerTagged() collections stay put because their matches do overlap and curated order is significant:

• TypeMapperInterface — ConstantArrayType extends ArrayType
• PhpParserNodeMapperInterface — FullyQualified extends Name
• AnnotationToAttributeMapperInterface — String (is_string) is a superset of ClassConstFetch (is_string && '::')

-        $this->registerTagged($rectorConfig, self::PHPDOC_TYPE_MAPPER_CLASSES, PhpDocTypeMapperInterface::class);
-        $this->registerTagged($rectorConfig, self::NODE_NAME_RESOLVER_CLASSES, NodeNameResolverInterface::class);
+        $rectorConfig->autodiscover(__DIR__ . '/../StaticTypeMapper/PhpDocParser');
+        $rectorConfig->autodiscover(__DIR__ . '/../NodeNameResolver/NodeNameResolver');

Both interfaces added to the class-leak skip list (their implementors are now discovered, not referenced). Verified each collection still resolves the same service count after boot (10 / 4), with no regression on the untouched collections (29 / 12).