fix: Not to bind core for connectionPlugin

[potsbo]

Problem

In typegen print process, using connectionPlugin always imports core from nexus even though the plugin doesn’t require.

Fixes

I tried to fix this by removing core from connectionPlugin bindings. However doing so leads to not importing core in any circumstances, which is sometimes required when dynamicInputFields and/or dynamicOutputFields is present. So I dug a bit deeper to find out following.

In current implementation, maybeAddCoreImport is called only when this.printImports[nexusSchemaImportId] is undefined, which basically means that there is no one configuring import from nexus package. I believe the origin of this behavior comes from this change.

This behavior is the reason why core was omitted when fixing bindings in connectionPlugin, because it tries to configure import from nexus.

Speculation about backward compatibility

The current behavior was introduced because of backward compatibility, which I think means not to break any current schema that manually importing core. If so, I believe my fix is better for those people because this can lead them to better state with less config.