feat: add factory class

[Niraj-Kamdar]

• closes: Implement Interface_Query_Factory to create Interface_Query from any URI #532

[dOrgJelli]

TODO:

• Add interface test to bind sanity test case. For example:

#import { Query } into Interface from "interface.eth"

type Query implements Interface_Query {
  ...
}

• Merge the Interface_Query and Interface_Query_Factory classes. A rough example of what this might look like:

class Interface_Query {
  static interfaceUri: string = "/ens/interface.eth";
  
  constructor(public uri: string) { }

  method(args: Input_method): string {
    w3_subinvoke(this.uri, etc);
  }
}

[Niraj-Kamdar]

From what I understand, we are going to use interfaces(InterfaceImplementedDefinition[]) property of QueryDefinition to see whether the imported namespace is interface or module, if it's imported and not in the interfaces it's a module and we won't be providing constructor for this and generating code for it like following so that user can directly use Ethereum_Query.method just like they've been doing.

class Ethereum_Query {
  static uri: string = "/ens/ethereum.eth";
  
  static method(args: Input_method): string {
    w3_subinvoke("/ens/ethereum.eth", etc);
  }
}

But in the case where it is in interfaces array, it will be interface and we will be generating code for this like:

class Interface_Query {
  static interfaceUri: string = "/ens/interface.eth";
  
  constructor(public uri: string) { }

  method(args: Input_method): string {
    w3_subinvoke(this.uri, etc);
  }
}

But doing it like this would require user to implement all the interfaces that he just want to use.
Ex: I have core polywrapper which uses token interface and for token interface there are USDC, DAI, and USDT
implementation polywrappers. From OOP perspective, there is only inheritance from token -> USDC, token -> DAI and token -> USDT. while we don't need to have token -> core inheritance but just need composition instead. So, I don't think it's a good idea to mark the core polywrapper as implementation of token interface polywrapper.

Let me know what do you think and whether I get it wrong.

[dOrgJelli]

Made an issue here to describe some future changes we might want to make: #547