fix: replace import.meta.resolve with require.resolve for Node 18+ compatibility

[irmowan]

Under Node 18+, the tsp-client convert tool met this issue:

TypeError: (intermediate value).resolve is not a function
    at getPathToDependency (file:///C:/nvm/v18.15.0/node_modules/@azure-tools/typespec-client-generator-cli/dist/utils.js:55:50)
    at convertCommand (file:///C:/nvm/v18.15.0/node_modules/@azure-tools/typespec-client-generator-cli/dist/commands.js:321:32)
    at async Object.handler (file:///C:/nvm/v18.15.0/node_modules/@azure-tools/typespec-client-generator-cli/dist/index.js:170:5)

In Node.js, there is no built-in import.meta.resolve() API. That function is a browser feature and isn’t implemented in Node 18 (nor in later versions at time of writing). If you need to resolve a module path in an ES module, the simplest solution is to use createRequire from the module package.

After I patched this commit in my local module, the issue is fixed.

[catalinaperalta]

Thanks for reaching out about this. Unfortunately, we require node 18.19+ to use tsp-client since we use several components that are not compatible with lower node versions. I wouldnt want to add this simply to try to support a lower node version for one command in the tool.