IModFile for nested jars not marked as IModFile.Type.LIBRARY when compared to NeoForge's NestedLibraryModReader

[MrCrayfish]

Minecraft version

1.20.1

Describe the bug

The creation of IModFile for nested jars (like Fabric API libraries) are not marked as a library.

Steps to reproduce

1. Load Sinytra Connector with Forgified Fabric API
2. Analyze ModFile#modFileType of any nested jar and it is not considered a library

Logs

No response

Additional context

The behavior seems to be inconsistent with NeoForge. NestedLibraryModReader from NeoForge treats all nested jars as a library and passes in IModFile.Type.LIBRARY in the IModFile#create method. This will help differentiate libraries from mods, and in mods like Catalogue, will be hidden in the mod list screen (if option is turned on).

Potentially offending lines:

Connector/src/main/java/org/sinytra/connector/locator/ConnectorLocator.java

Line 246 in ffe828a

IModFile modFile = IModFile.create(secureJar, JarModsDotTomlModFileReader::manifestParser);

Connector/src/main/java/org/sinytra/connector/locator/ConnectorLocator.java

Line 152 in ffe828a

IModFile modFile = IModFile.create(secureJar, f -> FabricModMetadataParser.createForgeMetadata(f, modPath.metadata().modMetadata(), modPath.metadata().visibleMixinConfigs(), modPath.metadata().generated()));