Replace Date with perf-hooks for time measurement

[TungstnBallon]

Currently, Jayvee uses Date to measure the duration of hooks, blocks and pipelines.

With this PR, the Jayvee interpreter now sets "performance marks" at relevant points during execution (before/after blocks/pipelines) and then measures the time between these marks. For now, marks are named with the following schema, with the goal of "encoding" the mark's location in the name:

`${pipeline name}::${block name}::${preBlockHook or BlockExecution or postBlockHook}::{start or end}`

This isn't final though, and I other ideas are welcome.

IMO this is a better approach than using the standard Jayvee hooks. Quoting #636 (comment):

As of now, the hooks' execution order is not sophisticated enough to log execution duration. Currently generic hooks are executed before block specific hooks in the order they are added. Considering #637, the hook logging execution duration would have to be executed after all other hooks, which cannot be guaranteed at this point.

I hope, that performance hooks can be used to implement a benchmarking tool using PerformanceObserver. That need's further testing though, so this PR is a draft for now.

[joluj]

Looks good! What's still missing?

[TungstnBallon]

Looks good! What's still missing?

I wanted to verify that this can actually be used to create a benchmarking tool (see #650).

[joluj]

Nice work!

Could you add a bit more documentation, especially to functions exported from the lib.

[joluj]

Awesome thank you!