Refactor path resolution

I believe the plan is to implement a Node.js-compatible resolver in StarlingMonkey, and if we are going to do this we should ensure the path handling logic is robust.

Refactoring the current path resolution to avoid the use of `new` could be a first step. We could also look at using `std::filesystem::path` in the implementation as well.