chore: optimize op_runtime_cpu_usage and op_runtime_memory_usage

[CyanChanges]

#27217

op_runtime_cpu_usage can be optimized by accepting a &mut [u32] instead of returning a serde tuple but it can be done as a follow up.

Accept a &mut [u32] instead of serde tuple for op_runtime_cpu_usage and op_runtime_memory_usage

[CyanChanges]

do we need to move the buffer here outside to avoid allocate memory each time?

[0f-0b]

u32 isn't wide enough to hold all possible return values.

$ deno eval 'new Uint8Array(2 ** 32); console.log(Deno.memoryUsage())'
{
  rss: 43925504,
  heapTotal: 7340032,
  heapUsed: 6022768,
  external: 4298203118
}

[CyanChanges]

u32 isn't wide enough to hold all possible return values.

$ deno eval 'new Uint8Array(2 ** 32); console.log(Deno.memoryUsage())'
{
  rss: 43925504,
  heapTotal: 7340032,
  heapUsed: 6022768,
  external: 4298203118
}

But it is not possible to use &mut [u64] in the ops i guess?

[CyanChanges]

or maybe we need read bigints from the buffer and cast them back to numbers?

[CyanChanges]

I checked Node.js's implementation, and now using Float64Array for this:

[littledivy]

LGTM, thanks!