Rewrite "prepareStackTrace" to use Rust API

[bartlomieju]

Currently CLI uses Error.prepareStackTrace API to perform source mapping and formatting of errors.

This situation leads to overall complexity of this method as well as requirement to manually acquire information about stack frames as well as distributing the logic between JS and Rust.

We want to avoid jumping between JS and Rust as much as possible and to solve this problem in this situation we need to:

1. Add new APIs to V8's StackFrame to acquire the same data as using CallSite:

deno/cli/rt/40_error_stack.js

Lines 172 to 191 in d68fb81

	function evaluateCallSite(callSite) {
	return {
	this: callSite.getThis(),
	typeName: callSite.getTypeName(),
	function: callSite.getFunction(),
	functionName: callSite.getFunctionName(),
	methodName: callSite.getMethodName(),
	fileName: callSite.getFileName(),
	lineNumber: callSite.getLineNumber(),
	columnNumber: callSite.getColumnNumber(),
	evalOrigin: callSite.getEvalOrigin(),
	isToplevel: callSite.isToplevel(),
	isEval: callSite.isEval(),
	isNative: callSite.isNative(),
	isConstructor: callSite.isConstructor(),
	isAsync: callSite.isAsync(),
	isPromiseAll: callSite.isPromiseAll(),
	promiseIndex: callSite.getPromiseIndex(),
	};
	}

2. Remove prepareStackTrace method from cli/rt/40_error_stack.js and instead use Isolate::set_prepare_stack_trace_callback - needs to be added to rusty_v8 first

CC @ry @nayeemrmn

[bartlomieju]

With recent improvements to error handling by @nayeemrmn done in #14378, #14394, #14302 and #14274 I feel this issue is no longer of high importance. Closing for now.