Resolve object correctly instead of through SQL

[worksofliam]

In the debugger code we are using SQL to resolve where the object exists on the system. Right now we are using the member path to find the library.

Instead, we should use the library list and then therefore our member resolve API to find the library and object.

https://github.com/codefori/vscode-ibmi/blob/master/src/api/debug/index.ts#L125

[mkwan01]

By default, debugger uses the compiler generated debug information to locate the debug source. If the source is not located on the compiler provided path, then we need a feature to add an additional source lookup path. The new source lookup path can be a local path or a remote path. We already have an open issue in debug client for this enhancement:
https://github.ibm.com/ibmi-toronto/debugclient/issues/62

This feature depends on work from the base debug service, which is owned by the system z team.

[worksofliam]

@mkwan01 I think this issue was to track an enhancement in our own code.

[heymchri]

Subscribing to this - I would love to see a way to point the debugger to the source location. We routinely transfer compiled programs to test systems where the source does not exist, so it would be very useful to be able to tell the debugger where the actual source is at. Having a way to point it at another system/partition would improve productivity considerably.