SCRIPTS: FIX #4081 Rerunning a script from tail window recalculates ram usage

[Snarling]

Fixes #4081

Previously the run button on a tail window was always using the cached ram calculation for the script from the first time the log box was spawned, due to the runningScript being the same object and this line from RunningScriptHelpers.ts:

bitburner/src/Script/RunningScriptHelpers.ts

Lines 4 to 7 in 2592c6c

	export function getRamUsageFromRunningScript(script: RunningScript): number {
	if (script.ramUsage != null && script.ramUsage > 0) {
	return script.ramUsage; // Use cached value
	}

Now rerunning a script using the run button will force a cost recalculation by resetting the ramUsage to 0 before relaunching, which disables this caching behavior.

Here is a test on current dev branch:

And here is the fixed result from this PR:

[phyzical]

should we consider moving this logic into startWorkerScript/ disable to caching to avoid this issue in other places or is it an expensive task?