Tool SubSchema Fields are Not Successfully Parsed on Tool Import

## Bug Summary
Subschema field is parsed as null on Tool Import

Description
When importing a Tool such as Tool 14, that also has dependencies on other Tools, and when its schema includes a subschema field type that is supposed to reference a dependency tool schema, the field is imported as Null. The subschema field also cannot be linked since the reference subschema dropdown only populates with the current tool's schemas.

## Steps to Reporduce
1. Import Tool 14
2. Import Tool dependencies Tools 13 (dependencies 03, 04, 05), Tool 06, Tool 05 (dependency Tool 07)
3. Link dependencies to published tools on local instance
4. Proceed with Import
5. Error displayed
6. Navigate to the Tool schema that threw the error
7. Inspect the field (which appears as String)

## Expected Result
- expect to import tool without errors
- expect subschema field to reference schemas from other tool via the drop down

## Actual Result
- error displayed
- cannot map subschema field type to reference schema's from other tools

## Artifacts